3 ms·
That's why you need a solid solution for DNS, though from my experience, mDNS does a decent enough job to solve it. Instead of the numbers you type in the host
by tscs37 9y ago
That's why you need a solid solution for DNS, though from my experience, mDNS does a decent enough job to solve it.
Instead of the numbers you type in the hostname of a device. IPv6 encourages to improve on the current lackluster DNS solutions some routers have.
- AstralStorm 9y agoHere, the linux routers are way ahead of you. Odhcpd used to handle ipv6 delegations for normal users can coordinate with dnsmasq (often used for ipv4 assignments and dns proxying) or unbound - to assign nice local names. Three trouble begins at internet scale where mDNS just does not work due to collisions. And ISPs do not want to give you free domain names and especially free dynamic subdomain delegation.
- tscs37 9y agoI use Pfsense which communicates DHCPv6 leases to Dnsmasq/Unbound fairly easily. >And ISPs do not want to give you free domain names and especially free dynamic subdomain delegation. Probably not but for internal resolution a .local or similar TLD is sufficient.
- AstralStorm 9y agoYes. The thing is, this would be super easy for the ISPs as they already have to maintain reverse DNS for dynamic IPv4 most of the time, so modifying it to also allow delegating to an authenticated DNS secret should be trivial. Eslecially now that ISPs are so fond of giving you big routers.