[148165] in North American Network Operators' Group
Re: IPv6 resolvers
daemon@ATHENA.MIT.EDU (Chris Adams)
Wed Jan 4 18:49:38 2012
Date: Wed, 4 Jan 2012 17:48:40 -0600
From: Chris Adams <cmadams@hiwaay.net>
To: nanog@nanog.org
Mail-Followup-To: Chris Adams <cmadams@hiwaay.net>, nanog@nanog.org
In-Reply-To: <79FBF1F6-F847-4A3D-85DF-9D1BF57FB59B@u13.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Once upon a time, Ryan Rawdon <ryan@u13.net> said:
> Try <random string>.pfsense.org (see below) to avoid caching, since the problem in question does not rely on the name existing. I am able to reproduce it roughly every 3rd random string I try, definitely not every time. I am unable to reproduce it with other domains so far, only pfsense.org and when it does occur I see a 1500-2200ms query time:
This appears to be a problem with the authoritative servers for
pfsense.org. They are dns[1-5].registrar-servers.com (which each have
multiple IP addresses). If I try each IP, I get no response from
38.101.213.194 and 2+ second response time from 69.16.244.25. Both of
those IPs are listed for dns1.registrar-servers.com.
--
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
