3 ms·

With IPv6 you would do stateless autoconfigurarion, so there would be no manually setting of your addresses. The router would advertise the new prefix and ever

With IPv6 you would do stateless autoconfigurarion, so there would be no manually setting of your addresses. The router would advertise the new prefix and everything would just use it. There would be no DNS configuration at all, all local machines would use anycast DNS for the services and a well known server for Internet addresses. One of the primary goals of IPv6 was to avoid needing manual configuration if anything on the network. It is supposed to be as automated as possible.

3np 3y ago
> There would be no DNS configuration at all, all local machines would use anycast DNS for the services and a well known server for Internet addresses. Assumptions and dragons be here.
- midasuni 3y ago
  MDNS, specifically designed for use on a single vlan, so useless
  - dfox 3y ago
    The solution there is DDNS, which is one of the things behind MS AD and just works, and configuring that on pure Unix infrastructure is surprisingly easy.
    - midasuni 3y ago
      Layers and layers of fragile interdependencies, and stop doesn’t remove the need for ipv4
midasuni 3y ago
And now I can’t find anything because mdns doesn’t work, half my kit won’t take dns entries, more fragility from systems which don’t exist, or and of course all my open sessions on local networks break as ip addresses change, not to mention all my WireGuard sessions.
TheHappyOddish 3y ago
> There would be no DNS configuration at all, all local machines would use anycast DNS for the services and a well known server for Internet addresses. Ok, lets say I have a web server - www.example.com running on 192.168.0.100:80/2001:db8::::::100 port 80 - and a game server - game.example.com running on 192.168.0.99:27015/2001:db8::::::99 port 27015. The IPv4 DNS A records point to a CNAME record of server.example.com, which has an A record for an IPv4 addrss which then forwards via NAT to the above. The IPv6 AAAA records point directly to the above addresses and go via a transparent firewall (which likely does router advertisement). How do I handle an address change when I change ISPs here? For IPv4 it's very simple - I update the CNAME record and there's no further configuration required - my NAT works and traffic flows. Assumedly I could automate this simply with a DDNS client my router likely already has built in. For IPv6, I presume I need to look up all the machines (likely via logging into them as DHCPv6 doesn't appear the norm), then go through an update all records? I understand a static suffix may help on inferring the new address, but surely I either have lots of manual updating to do now or need to run a DDNS client per machine? I have tried running a dual stack, but every time I try it seems to be significantly more steps and complexity than IPv4, but maybe I'm missing something.
- p1mrx 3y ago
  I think a DDNS client per device is the simplest solution. With https://dns.he.net https://dns.he.net, this can be an hourly cron job that fetches a URL, so no additional software is needed. Alternatively, if your devices have a stable suffix, https://dynv6.com/ https://dynv6.com/ supports prefix updates across multiple records.
  - TheHappyOddish 3y ago
    > I think a DDNS client per device is the simplest solution. With https://dns.he.net https://dns.he.net, this can be an hourly cron job that fetches a URL, so no additional software is needed. Sure, but depending on what you have set up a lot of maintenance and complexity compared to NAT. > Alternatively, if your devices have a stable suffix, https://dynv6.com/ https://dynv6.com/ supports prefix updates across multiple records. That is cool and interesting, thanks! Like a lot of people self hosting, the hosted nature of it is unappealing to be, but the concept is workable with a self-hosted solution for sure.

3np 3y ago

> There would be no DNS configuration at all, all local machines would use anycast DNS for the services and a well known server for Internet addresses. Assumptions and dragons be here.

midasuni 3y ago
MDNS, specifically designed for use on a single vlan, so useless
- dfox 3y ago
  The solution there is DDNS, which is one of the things behind MS AD and just works, and configuring that on pure Unix infrastructure is surprisingly easy.
  - midasuni 3y ago
    Layers and layers of fragile interdependencies, and stop doesn’t remove the need for ipv4

midasuni 3y ago

And now I can’t find anything because mdns doesn’t work, half my kit won’t take dns entries, more fragility from systems which don’t exist, or and of course all my open sessions on local networks break as ip addresses change, not to mention all my WireGuard sessions.

TheHappyOddish 3y ago

> There would be no DNS configuration at all, all local machines would use anycast DNS for the services and a well known server for Internet addresses. Ok, lets say I have a web server - www.example.com running on 192.168.0.100:80/2001:db8::::::100 port 80 - and a game server - game.example.com running on 192.168.0.99:27015/2001:db8::::::99 port 27015. The IPv4 DNS A records point to a CNAME record of server.example.com, which has an A record for an IPv4 addrss which then forwards via NAT to the above. The IPv6 AAAA records point directly to the above addresses and go via a transparent firewall (which likely does router advertisement). How do I handle an address change when I change ISPs here? For IPv4 it's very simple - I update the CNAME record and there's no further configuration required - my NAT works and traffic flows. Assumedly I could automate this simply with a DDNS client my router likely already has built in. For IPv6, I presume I need to look up all the machines (likely via logging into them as DHCPv6 doesn't appear the norm), then go through an update all records? I understand a static suffix may help on inferring the new address, but surely I either have lots of manual updating to do now or need to run a DDNS client per machine? I have tried running a dual stack, but every time I try it seems to be significantly more steps and complexity than IPv4, but maybe I'm missing something.

p1mrx 3y ago
I think a DDNS client per device is the simplest solution. With https://dns.he.net https://dns.he.net, this can be an hourly cron job that fetches a URL, so no additional software is needed. Alternatively, if your devices have a stable suffix, https://dynv6.com/ https://dynv6.com/ supports prefix updates across multiple records.
- TheHappyOddish 3y ago
  > I think a DDNS client per device is the simplest solution. With https://dns.he.net https://dns.he.net, this can be an hourly cron job that fetches a URL, so no additional software is needed. Sure, but depending on what you have set up a lot of maintenance and complexity compared to NAT. > Alternatively, if your devices have a stable suffix, https://dynv6.com/ https://dynv6.com/ supports prefix updates across multiple records. That is cool and interesting, thanks! Like a lot of people self hosting, the hosted nature of it is unappealing to be, but the concept is workable with a self-hosted solution for sure.