[Yeti DNS Discuss] One funny naming scheme for root name servers, to test

Stephane Bortzmeyer bortzmeyer at nic.fr
Wed Apr 6 18:51:02 UTC 2016

Suggestion from Paul Hoffman: use just one name, and one IP address
per server. So, for instance:

.             IN    NS     the-real-and-only.root.
the-real-and-only.root.  IN AAAA 240c:f:1:22::6
                         IN AAAA 2a01:4f8:161:6106:1::10
                         IN AAAA 2001:e30:1c1e:1::333
                         IN AAAA 2a02:ec0:200::1
                         IN AAAA 2001:4b98:dc2:45:216:3eff:fe4b:8c5b
                         IN AAAA 2001:67c:217c:6::2
                         IN AAAA 2a02:2810:0:405::250
                         IN AAAA 2001:6d0:6d06::53
                         IN AAAA 2001:1398:1:21::8001
                         IN AAAA 2001:559:8000::6
                         IN AAAA 2001:200:1d9::35
                         IN AAAA 2604:6600:2000:11::4854:a010
                         IN AAAA 2001:620:0:ff::29
                         IN AAAA 2a02:cdc5:9715:0:185:5:203:53
                         IN AAAA 2001:1608:10:167:32e::53

In theory, it should work because RFC 1034 is crystal-clear: "[in case
of failure] The client should try other servers and server addresses
before repeating a query to a specific address of a server." So, the
client, the resolver, will try all the IP *addresses* of
the-real-and-only.root before giving in.

On the other hand, not every implementer reads the RFC and some
resolvers will try only other *names* and thus failed the first time
they will encounter a problem.

A good way to test it would be to add deliberately unreachable
addresses to the above set.

More information about the discuss mailing list