Can you please add functionality that will allow to configure dns settings on client computers via DHCPv6? Windows does supports dns configuration via DHCPv6 and does not supports via ND.
Thanks.
This feature is already added since 6.0rc4
Unfortunately i can’t find it, can you please tell me, where i can configure it?
add ipv6 address to /ip dns servers and dhcp will take that address automatically.
Are there plans to allow for different IPv6 DNS servers for each DHCP server network?
With the way the feature is implemented right now, you cannot hand out only the address of your local caching nameserver(s). You could add the local nameservers to the list of the servers used as forwarders by the DNS server, but that means users could end up bypassing the local caching nameserver. For IPv4, this isn’t really and issue too much when using NAT(dstnat rules can direct the traffic), but it is an issue with IPv6.
Right, there’s a problem here. And it applies also to DNS in RA.
I like DNS cache on RouterOS and its ability to set static records. It makes great “poor man’s DNS server” for local hostnames on smaller setups (anything where dedicated DNS server, including Metarouter-based one, would be an overkill). Router has some external servers in “/ip dns” and clients behind router get its internal address as DNS server.
With IPv4 it worked great. With dualstack it’s still manageable. Clients either don’t get IPv6 DNS servers at all, because ISP does not supply them, or in worst case they can be blocked (if there are some IPv4 ones left). But I currently see no solution for IPv6-only. It’s not too pressing right now, but it should be solved before it changes.
With IPv4 it’s easy, usual setup with private addresses is static, router’s internal address does not change. But with IPv6 dynamic prefixes it’s a little more complicated. So in addition to option to set custom servers, it would also need another option to use router’s current address. It could be solved by script (if there’s an option to set custom servers), but such basic things should have direct options.
Sorry for waking up a zombie thread. But the Windows client doesn’t appear to be able to get DNS from DHCPv6 despite what is said in this thread.
Seems the change is only relevant to DHCPv6-PD usecase not for clients..