Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

RDNSS Support in IOS

According to Wikipedia, IOS supports RDNSS or the abillity to configure IPv6 DNS Server(s) via RA (RFC 6106):

http://en.wikipedia.org/wiki/Comparison_of_IPv6_support_in_operating_systems

However, I can't figure out how to set this up.  Can someone provide an example of this or point me to the appropriate document?

Thanks,

  --Jim

Everyone's tags (5)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: RDNSS Support in IOS

Jim,

No, IOS does not have the code implementing support for rfc6106 at the moment - you would need to use stateless DHCPv6, and set Other flag in the RAs.

That said, in my practice every client that might do rfc6106 would do stateless DHCPv6 fine, so would be useful to learn more about the requirements of your setup.

--a

Sent from Cisco Technical Support iPhone App

6 REPLIES
Cisco Employee

Re: RDNSS Support in IOS

Jim,

No, IOS does not have the code implementing support for rfc6106 at the moment - you would need to use stateless DHCPv6, and set Other flag in the RAs.

That said, in my practice every client that might do rfc6106 would do stateless DHCPv6 fine, so would be useful to learn more about the requirements of your setup.

--a

Sent from Cisco Technical Support iPhone App

Community Member

Re: RDNSS Support in IOS

Hi Andrew - are you telling me Wikipedia is not infallible?  :-)  So I agree that stateless DHCPv6 should generally suffice.  However, RDNSS support would be nice.  Some good use cases:

1) The Internet Of Things - In the embedded market, full DHCPv6 support would be harder - RDNSS would be much more appealing

2) Labs/Test environments - Anything to facilitate the rapid deployment of test/lab networks would be a boon.  While DHCP/DHCPv6 isn't hard to setup, using RAs is brain dead and the ability to add a simple option to include DNS would be fantastic.

3) SOHO - Again, for simple environments this would be a plus.  Also, when our Refridgerators and Coffee Makers join the network I would think RDNSS would be easier than stateless DHCPv6.  Did you have a chance to see how the Internet of Things will hook us up:

http://blogs.cisco.com/news/the-internet-of-things-infographic/

Please let me know what you think and if I may say, great job with Happy Eyeballs.  I was very pleased to find out this is implemented in Windows 8 and Server 2012.

--Jim

Cisco Employee

Re: RDNSS Support in IOS

hi Jim, thanks for the kudos and the use cases!

Definitely want to discuss this a bit more!

re. use cases:

1) internet of things: yes, quite probably... But if we talk sensors and other constrained devices, would rfc6106 still apply, given that these networks will probably be special case governed by ROLL/6LoWPAN IETF WG work ? (http://datatracker.ietf.org/wg/roll/charter/, http://datatracker.ietf.org/wg/6lowpan/charter/ - especially RFC4919. I'll ask the folks involved in those WGs what they think.)

2) LAB/test machines: Let me challenge this :-). In my lab for IPv6-only client test setup I use Stateless DHCPv6, works fine for all major modern OSes. (Ubuntu added it in 12.04, http://www.stgraber.org/2011/07/26/state-of-ipv6-in-ubuntu-oneiric/). Note, that I still use SLAAC for the IPv6 address assignment, so the addresses are stable EUI-64, thus no state on the IOS DHCPv6 server.  (NB: Android, sadly, is not yet in this happy group. See http://code.google.com/p/android/issues/detail?id=3389#c107)

3) SOHO: not sure. Assuming the discussion is about the coffee machines (the consumer general purpose OSes would be covered in (2) above) - would depend which kind of code they will run. With the advent of the SoCs like RaspberryPi, the concern about the a few bytes of code space required to run DHCPv6, would no longer hold imho. And I'd be willing to bet that the coffee machine producers will use linux-based hardware to lower the development costs and TTM. What do you think ?

A couple of comments/questions about the implementation:

Do you have any practical experience with the issues mentioned in http://tools.ietf.org/html/draft-gont-6man-slaac-dns-config-issues ? To me seems like the corner cases still need to be a bit hashed out.

As for the difficulty of the DHCPv6 implementation: here's a relevant "server" part that I used in my CL12 San Diego "network hijack" demo. Granted, it's a quick and ugly hack script that used scapy libs (and it is only the server side, I did not write the client side code, and in C it would be a bit more verbose of course):

                if DHCP6_InfoRequest in pkt:

                        print "DHCP Information request"

                        print (pkt[IPv6].src)

                        rep = Ether(src=get_ether_src(),dst=pkt[Ether].src)/\

                                IPv6(dst=pkt[IPv6].src)/\

                                UDP(sport=31337,dport=546)/\

                                DHCP6_Reply(trid = pkt[DHCP6_InfoRequest].trid)/\

                                pkt[DHCP6OptClientId]/\

                                DHCP6OptOptReq(reqopts=[24,23,32])/\

                                DHCP6OptServerId(duid=DUID_LLT(lladdr=get_if_hwaddr(scapy.config.conf.iface6)))/\

                                DHCP6OptDNSDomains(dnsdomains=["hijacked.invalid"])/\

                                DHCP6OptDNSServers(dnsservers=[dns64_address])/\

                                DHCP6OptInfoRefreshTime(reftime=300)

                        sendp(rep, verbose=False)

But, just using this to illustrate that for the stateless DHCPv6 the coding is not too hard. And, unlike the RDNSS, it's fully in userspace on the clients. Which may play a role if any tweaks/changes are needed to implementation.

FWIW, I realise the above looks a like a giant excuse "why we don't do it", I ought to mention that last year I did make an experimental image that had a proof-of-concept code for RFC6106, but had a bit of a hard time gathering the business case that would allow me to solicit for any "official" efforts in this area. If you have or have had real projects that would be critically dependent on RDNSS, I'd be very interested - ping me via email with that.

--a

Community Member

RDNSS Support in IOS

A good use case is that one of our customer mandates RDNSS support, so we have to use it internally for development.

Cisco Employee

RDNSS Support in IOS

@Erwan: this is indeed very good use case. I'd be interested to chat more about details - would you be able to ping me via mail ?

Community Member

RDNSS Support in IOS

My router Linksys E4200 does not support DHCPv6, but supports configuration DNS through RA (RFC6106).

3987
Views
0
Helpful
6
Replies
CreatePlease to create content