2 ms·
> each device needs a DynDNS client configured My home router does something even better out of the box: Every device that's hostname.local or hostname.my.rout
by lxgr 6y ago
> each device needs a DynDNS client configured
My home router does something even better out of the box: Every device that's hostname.local or hostname.my.router locally is also globally resolvable through hostname.myusername.routervendor.com.
This is basically DnyDNS at the router level, rather than the device level (which has many downsides as you describe), and it's been a game changer for my IPv6 home use.
- craftkiller 6y agopfsense (the router magicalhippo is using) also supports this. Its under Services > DHCP Server (and/or DHCPv6 Server) > Dynamic DNS
- magicalhippo 6y agoThat seems to require a RFC 2136 compatible DNS server on the other end, yes? So my regular dyndns ain't gonna cut it I assume.
- Dagger2 6y agoHow did we end up in this world where regular DNS updates aren't considered to be "regular dyndns" :/
- magicalhippo 6y agoNot my area, but what I can say is that the DNS provider I've used for ages (Domeneshop) does not support RFC 2136. So I guess I either have to switch (to who?) or I set up some alias and run my own bind (another service to admin, yay). Or am I missing something?
- Dagger2 6y agoI run my own copy of bind, and use https://dns.he.net https://dns.he.net as a slave pulling the zones from it. As a result I can actually use all DNS features. I find it super frustrating that most dynamic DNS providers use their own custom API rather than just using the update mechanism that's in the protocol itself. That said, if they support v6 then you can probably use them by installing their update client on each machine that you want a hostname for. It just won't integrate with pfsense.