Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In ipv4 I can set my DHCP server to populate DNS with hostnames and IP addresses as clients are found. This works well and clients can resolve these DNS addresses to contact eachother over routed subnets. How can this be done in ipv6 without DHCP?

Link Local Multicast Name Resolution can allow clients on the same subnet to discover eachothers hostnames and match them to link-local addresses, but so far I can't find a way for clients to advertise their global or unique local addresses and hostnames to a DNS server to be resolved across subnets.

share|improve this question
Are you not using DHCP for your IPv6 network? Why wouldn't your DHCP server update the DNS zones also? – Zoredache Sep 27 '12 at 20:26
@Zoredache because DHCPv6 is only one of the two popular ways of assigning IP addresses to hosts in LANs under IPv6 and it is by far the heavier and less automatic of the two. The other one is SLAAC. – Celada Sep 27 '12 at 20:29
I don't really know what best practices around this are going to eventually fall out. Personally, I wrote a small utility (in C) for Linux which watches for changes in interface IP addresses and registers the current set in DNS using dynamic DNS (the real DDNS that is part of the DNS protocol, not the nonsense from & co.). Each host is thus responsible for registering itself (and has a copy of the shared TSIG key to do it). – Celada Sep 27 '12 at 20:34
@Celada, perhaps I am missing something, but I didn't think SLAAC could deliver settings like the IPv6 address(s) of your DNS server(s). I thought DHCP was pretty much required. Either that or maybe some kind of Multicast DNS setup. – Zoredache Sep 27 '12 at 21:54
SLAAC can in fact deliver IP addresses of DNS servers, but it is true that DHCPv6 is required for some of the fancier options like NTP server or netboot parameters. Still, those options can be delivered using stateless DHCP while still using SLAAC for the actual address assignment. That's advantageous because stateless DHCP is much more lightweight than stateful DHCP (which is required if using DHCP for address assignment). – Celada Sep 27 '12 at 22:34

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.