On Mon, January 11, 2010 6:27 pm, Miles Mccredie wrote: > FWIW, this is what I'm seeing from an IPv4 only host. Not sure if the > unexpected source is the problem that kloth.net is seeing or whether > it's the result of putting
>> *;; reply from unexpected source: 77.103.161.36#60741, expected >> 77.103.161.36#53 >> ;; reply from unexpected source: 77.103.161.36#60741, expected >> 77.103.161.36#53 >> ;; connection timed out; no servers could be reached It never rains but it pours?! I too have seen that on occasion. I think it's down to my crappy D-Link router, or rather its implementation of NAT. I've got a Cisco router sat here waiting to take its place when I can find time to get round to it. > FWIW, at least one of the afilias hosts had the same IPv4 address for > ns[12].v6ns.org. >> ns1.v6ns.org. 86400 IN A 77.103.161.36 >> ns1.v6ns.org. 86400 IN AAAA 2a01:348:133::a1 >> ns2.v6ns.org. 86400 IN A 77.103.161.36 >> ns2.v6ns.org. 86400 IN AAAA 2a01:348:6:a1::2 Hmm.. That's interesting. I know for a fact that my registrar wouldn't allow me to enter two servers with the same address, however within my zone I may have had ns[12] set with IPv4 records set for a period (a few days ago). This makes me wonder where .org is getting its records from - a combination of glue provided by the registrar and cached results from my zone? Mathew _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users