none
Windows and support for IPv6 RFC 6106 / RDNSS (Router Advertisement Options for DNS)

    Question

  • How do we enable Windows clients to accept Router Advertisement Options for DNS (IPv6 RFC 6106 / RDNSS). All of our other clients (Linux, iOS, MacOs, Android, etc.) are natively supporting DNS configuration via Router Advertisement. However, it seems that neither Windows 10, Server 2012 nor Server 2016 supports this IPv6 feature yet - or is there a way to enable this? If not when will it be supported?

    Kind regards,
    Anders




    Monday, January 4, 2016 8:54 PM

Answers

  • Hi Anders,

    "I seems quite old-school having to manage DHCPv6 scopes just for implementing a feature which is already built into IPv6. Also, since the book was published, it seems that RDNSS have become a wide spread standard in IPv6 networks and has been adopted by most other platforms out there - except Windows..."

    First IPv6 proposal didn't contain RDNSS and people in IETF always argued, that putting DNS info into RA message is a layer violation (information from the application layer is inserted into a message from the network layer). Thus, the "pristine" solution, according to many people in IETF, is to use RA just for addressing and routing and DHCPv6 for everything else. (You will hear the same arguments if you asked why DHCPv6 doesn't support prefix information for assigned address and default gateway.) These religious wars are still present and if you watch NANOG or other mailing lists, you will see it every half year. One camp would like to have feature parity, other camp wants "clean" design.

    So Microsoft is actually doing things "right" here. Thus, I don't think that Microsoft changes it's mind. However, I absolutely agree with you that from an operation point of view, it is a problem and the situation could be much better.

    M.


    Tuesday, January 5, 2016 6:18 PM

All replies

  • Hello Anders,

      as far as I know, Microsoft doesn't support RDNSS and doesn't plan to support it either. Here is Edward Horley's citation from his book Practical IPv6 for Windows Administrators:

    "Microsoft has publicly stated that it does not intend to develop any support for RFC 6106 into Windows. It is

    my understanding that Microsoft feels that any organization that wishes to publish DNS information will use either DHCPv6 Stateful or Stateless to provide that function."

    Sincerely,

      Matej

    Tuesday, January 5, 2016 8:17 AM
  • Hi Matej,

    Thanks for the reply. I have seen the statement from Edward's book before. However, the book is from 2013/2014 and one could hope, that Microsoft have changed their strategy, as the world is adopting IPv6.

    I seems quite old-school having to manage DHCPv6 scopes just for implementing a feature which is already built into IPv6. Also, since the book was published, it seems that RDNSS have become a wide spread standard in IPv6 networks and has been adopted by most other platforms out there - except Windows... 

    There are hacks available, like the RDNSS Daemon for Win32, but that doesn't seem to be an enterprise ready solution...

    It would be great to see an updated statement from Microsoft in regards to RDNSS. They work hard to push IPv6 usage into all areas of Windows, so it seems weird that they only offer an amputated implementation of IPv6 and DNS.

    /Anders


    Tuesday, January 5, 2016 4:09 PM
  • Hi Anders,

    "I seems quite old-school having to manage DHCPv6 scopes just for implementing a feature which is already built into IPv6. Also, since the book was published, it seems that RDNSS have become a wide spread standard in IPv6 networks and has been adopted by most other platforms out there - except Windows..."

    First IPv6 proposal didn't contain RDNSS and people in IETF always argued, that putting DNS info into RA message is a layer violation (information from the application layer is inserted into a message from the network layer). Thus, the "pristine" solution, according to many people in IETF, is to use RA just for addressing and routing and DHCPv6 for everything else. (You will hear the same arguments if you asked why DHCPv6 doesn't support prefix information for assigned address and default gateway.) These religious wars are still present and if you watch NANOG or other mailing lists, you will see it every half year. One camp would like to have feature parity, other camp wants "clean" design.

    So Microsoft is actually doing things "right" here. Thus, I don't think that Microsoft changes it's mind. However, I absolutely agree with you that from an operation point of view, it is a problem and the situation could be much better.

    M.


    Tuesday, January 5, 2016 6:18 PM
  • So I guess the best way is to enable the "O" flag in the router's RA's and then run a DHCPv6 server which is only responsible for providing DNS configuration data.

    In that way IPv6 hosts will auto-configure their addresses via NDP, but ask DHCPv6 for any additional config parameters, e.g. DNS servers.

    /Anders

    Wednesday, January 6, 2016 2:49 PM
  • Windows 10 v1703 supports RDNSS now. (But there is no official document yet to mention this.)
    Thursday, April 13, 2017 8:58 AM