I have been using queries like these to test: dig any . @f.root-servers.net | egrep "(DiG 9|AAAA)" dig +bufsize=1400 any . @f.root-servers.net | egrep "(DiG 9|AAAA)" The first offers up a standard DNS query, the second an EDNS0 query of 1400 bytes. In a standard query you're only going to get 3 AAAA records, EDNS0 should allow for all of them. There are currently 6 servers with AAAA records: % dig any . @f.root-servers.net | egrep "(DiG 9|AAAA)" ; <<>> DiG 9.5.0b2 <<>> any . @f.root-servers.net A.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:503:ba3e::2:30 F.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:500:2f::f H.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:500:1::803f:235 % dig +bufsize=1400 any . @f.root-servers.net | egrep "(DiG 9|AAAA)" ; <<>> DiG 9.5.0b2 <<>> +bufsize=1400 any . @f.root-servers.net A.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:503:ba3e::2:30 F.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:500:2f::f H.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:500:1::803f:235 J.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:503:c27::2:30 K.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:7fd::1 M.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:dc3::35 It is also the case that various servers are still getting up to date; virtually all the root servers are more than one machine either load balanced or anycasted. As a result YMMV until everything is in sync again. Rest assured, those who run root servers are paying very close attention today. I've already helped people fix two problems, both a result of ISP's filtering the RIR's micro-allocation blocks in ways they should not be doing. Please, if you have IPv6 filters make sure you've updated them to allow down to a /48 in the various RIR's micro allocation blocks (recently posted to nanog by someone else). -- Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/