Hi everyone. I’ve managed IPv6 to my LAN, in IPv6 network discovery I’ve enabled DNS advertising and advertising IPv6 address itself from prefix. My laptop got addresses and DNSv6 too. PC’s with win 8.1 also got addresses, but didn’t get dnsv6 servers addresses. Is it true that windows OS can’t install dnsv6 servers from 25 protocol of IPv6?
Microsoft only added support for DNS from RA not so long ago. And as far as I know, only to Windows 10, no backports. But you can use DHCPv6, RouterOS supports stateless server.
You mean I need to manage dhcpv6 server + IPv6 advertising?
You already have advertising, so you just need to enable other config in options, add DHCPv6 server to same interface without specifying pool and it will work in stateless mode and provide info to clients that ask (as instructed by other config flag in RA).
That’s what I meant. Will try, thanks! 
Stateless DHCPv6 not working. Works only ND and RA and static DNSv6.
Can anyone confirm this?
So “now working” or “not working”? It works for me and with current RouterOS, you can use any options you need (the interface for options if not very friendly yet, but it works).
RouterOS config:
/ipv6 address
add address=2001:db8::1/64 interface=ether3
/ipv6 nd
set [ find default=yes ] other-configuration=yes
/ipv6 dhcp-server option
add code=23 name=dnsrecursivenameserver value=0x20010db800000000000000000000000220010db8000000000000000000000003
add code=24 name=domainsearchlist value=0x076578616d706c65036e657400076578616d706c6503636f6d00
/ipv6 dhcp-server
add dhcp-option=dnsrecursivenameserver,domainsearchlist interface=ether3 name=server1
Connected Windows 8.1:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : example.net
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
Physical Address. . . . . . . . . : 00-0C-29-46-67-17
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:db8::adcd:16f7:b9b5:6516(Preferred)
Temporary IPv6 Address. . . . . . : 2001:db8::14a5:337e:7a50:8ea0(Preferred)
Link-local IPv6 Address . . . . . : fe80::adcd:16f7:b9b5:6516%3(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.101.22(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : fe80::20c:29ff:feef:fd4%3
DHCPv6 IAID . . . . . . . . . . . : 50334761
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-0A-34-DF-00-0C-29-46-67-17
DNS Servers . . . . . . . . . . . : 2001:db8::2
2001:db8::3
NetBIOS over Tcpip. . . . . . . . : Enabled
Connection-specific DNS Suffix Search List :
example.net
example.com
If you don’t define any DHCPv6 option, server will by default take DNS resolvers from “/ip dns”, if there are any.
Sorry for misunderstanding about “now”. It was “not”.
If I set “other options” with dhcpv6 server active on advertising interface, I will not get dnsv6 servers to my PC. DNSv6 are set in IP - DNS. There are v4 and v6 servers. I know about dhcp options, but did not try yet. I need the server to get dnsv6 from IP - DNS. ROS 6.42.1.
No problem with that either:
/ip dns
set allow-remote-requests=yes servers=192.168.80.1,192.168.80.3,2001:db8::4,2001:db8::5
/ipv6 address
add address=2001:db8::1/64 interface=ether3
/ipv6 nd
set [ find default=yes ] other-configuration=yes
/ipv6 dhcp-server
add interface=ether3 name=server1
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
Physical Address. . . . . . . . . : 00-0C-29-46-67-17
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:db8::adcd:16f7:b9b5:6516(Preferred)
Temporary IPv6 Address. . . . . . : 2001:db8::a465:670:f11a:95be(Preferred)
Link-local IPv6 Address . . . . . : fe80::adcd:16f7:b9b5:6516%3(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.101.22(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : fe80::20c:29ff:feef:fd4%3
DHCPv6 IAID . . . . . . . . . . . : 50334761
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-0A-34-DF-00-0C-29-46-67-17
DNS Servers . . . . . . . . . . . : 2001:db8::4
2001:db8::5
NetBIOS over Tcpip. . . . . . . . : Enabled
I’d try packet sniffer on client, it will immediatelly show if it receives correct RA, if it sends DHCPv6 request, and what it gets back.
I think I’ll prefer to use just slaac, without statless dhcpv6. Will wait for statefull dhcpv6. But thanks for your answers and help!
Well, unless you’re doing IPv6-only network, you can easily live without IPv6 resolvers, system will use IPv4 ones. Both can return all records.
It’s nice that ipv6 has priority over ipv4 It is so unusual that ipv4 now more in support role.
What I like most is having them both, it’s like a backup connection for free. Make a mistake in firewall config, lock yourself out … and there’s no need to worry, because you can still connect using the other protocol. It actually happened to me only few times over the years, and I wasn’t always even the person who got locked out, but it’s nice to have it as option.
IPv4 as the other (less important) protocol sounds nice, but it will take a lot of time, before it happens everywhere. There are still too many stubborn people who honestly believe that IPv6 will lose and they will get shiny new IPv7. Something better, because it won’t be “overcomplicated as IPv6”, but “simple like IPv4, only with more addresses”.
I guess I will miss NAT, when IPv6 finally rules the world. I mean, I will be glad to get rid of it, of course. But we had so many exciting experiences together, it will be like losing life-long companion. 
Strange, doesn’t work for me.
I get in the mkt logs “handling only prefix delegation discarding” , Mkt seems to only delegate prefix through DHCP, no IA for single stations.
I can’t make DHCPV6-server work for hosts (tried Windows host) , and I can’t make DNS pass through DHCP for Windows hosts. SLAAC works fine (but with no DNS provided).
That’s correct, addresses are not supported yet. But DNS (and other options, if you add them) from DHCPv6 works. Don’t forget the other-configuration=yes in /ipv6 nd, it’s what tells clients to ask DHCPv6.
That’s what I do , but my Windows client asks for an address , even if I say that I use SLAAC. And it won’t get an adress through DHCP , thus it stucks at renewing its IPV6.
Windows 8.1 is the target.
How client gets address and other info depends on router advertisements, and you control those (options in “/ipv6 nd”). Look at what I posted in this thread before, it’s minimal working config and you can also see what Windows client does with it. Do you have something significantly different in yours?
I have the same configuration yes :-p
So definitely not managed-address-configuration=yes?