Comment on How do people handle authoritative DNS redundancy for their self-hosted workloads?
buedi@feddit.org 1 day agoMay I ask how you got this started? Hosting your own ASN, as far as I understand only works if my ISP would actually route traffic to my ASN, right? I am thinking about getting into IPv6 for self-hosting and I could ask my ISP to change my current setup (I only have IPv4, but a public one, without CGNAT) and I do not trust them that they mess this up. So my preferred way would be to not touch anything on the ISP side and host my own ASN and find a Sponsor for a /48 Block. I still cannot wrap my head around this.
Just that I understand you correctly: You got your ASN and /48 block from RIPE (or a Sponsor I assume) and you host your own AS? Or is the AS hosted by someone else? If the latter, I wonder how traffic can find to your home or to your Server locations.
Nothing of this would work without getting in touch with my ISP, and I fear the usual resedential IPs will not care.
farcaller@fstab.sh 1 day ago
First on how to get an ASN: you can buy it for reasonably cheap from a LIR. Some will even toss a free /48 with that. Happy to offer names in private so that there’s no advertising. Expect a budget quoted above.
Once you have an ASN, you need to get an upstream - actually two as RIPE mandates at least two (otherwise why’d you need an ASN). Some LIRs would offer transit with ASN purchase. You can upstream via your ISP, if they allow you to (that’s very rare). Another option is a tunnel (there are free and paid ones) or a VM somewhere (some cloud providers offer to set up bgp with VMs they host). Generally, free ones are enough for basic stuff. Not much bandwidth and oftentimes IPv6 only, but you don’t pay anything either. Besides, you can ask around in various network related chats. Practically, I can offer ip transit with some marginally low burstable bandwidth, and that’s pretty common. You can look/ask around https://discord.gg/ipv6 for example.
For getting ASN to your homelab you’re looking at a tunnel option, most probably. Great if you have static ipv4 - allows you to use more common tunnels, but is still doable with a floating IP (e.g. check bgptunnel).
buedi@feddit.org 19 hours ago
Thank you very much for your reply. So the bottomline is, that when bound to a residential ISP, we most likely have no chance to utilize our own AS and IPv6 Prefix without the help of a 3rd party (ASN peering aside, which is needed of course, no matter what). So it’s usually involving tunnels to get it up and running. That solves the mystery somewhat for me and I think I know in which direction I have to do my research.
I think I will start prototyping with route64 (which you mentioned above), but if I get this up and running, I would appreciate it if you could PM me the LIRs you have on your list. If I can wrap my head around this, if the fees are still in the ballpark you mentioned above, that sounds very reasonable to use this in my Homelab and gather experience with IPv6 and AS.
Thanks again for your help :-)