Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Can't answer your main question, but from what I recall, DHCPv6 is kind of necessary anyway. It's the easiest/main way for the client to receive DNS server information, even if default gateway discovery is now down through multicast.

I believe there is another way, but the router has to support it and I forget what it's called.



RA (Router Advertisement) handles announcing the prefix for SLAAC addresses and DNS.


But not other services like NTP, so DHCPv6 is still needed.


Create a DNS name ntp.yourdomain.example.org that points at your internal ntp servers.

Configure your ntp clients to use the name, and maybe add a pool.ntp.org entry or two into your configs.


> Configure your ntp clients to use the name

So how do you do this hands-off, ie without manually changing things on the clients, without DHCPv6?


For NTP, an alternative is letting the LAN devices connect to whatever NTP server they want to, and just NAT'ing outgoing udp/123 to your NTP server.


Well yes, but that's a suboptimal hack.


yes, but RDNSS is a relatively new option (only since 2007 ;) ), so some implementations ignore it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: