On Jan 4, 2012, at 3:46 PM, Mark Kamichoff wrote:
On Wed, Jan 04, 2012 at 09:39:39PM +0100, Seth Mos wrote:
And a similar mistake I see others respond too as well, this is another domain with just a IPv4 record. That was not really what I was complaining about but I was not specific enough in my email
When requesting the DNS for the hostname with a Quad A the story is entirely different!
Try www.pfsense.com or www.didi.nl
Still not seeing additional latency from here:
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: nova-dhcp-host111:~ ryan$ dig @ordns.he.net awegawregwaefg.pfsense.org ; <<>> DiG 9.6.0-APPLE-P2 <<>> @ordns.he.net awegawregwaefg.pfsense.org ; (2 servers found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24807 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;awegawregwaefg.pfsense.org. IN A ;; AUTHORITY SECTION: pfsense.org. 3600 IN SOA dns1.registrar-servers.com. hostmaster.registrar-servers.com. 2012010200 10001 1801 604801 3601 ;; Query time: 1695 msec ;; SERVER: 2001:470:20::2#53(2001:470:20::2) ;; WHEN: Wed Jan 4 18:34:17 2012 ;; MSG SIZE rcvd: 117 nova-dhcp-host111:~ ryan$
(neodymium:15:44)% dig @2001:470:20::2 www.didi.nl. AAAA
; <<>> DiG 9.7.3 <<>> @2001:470:20::2 www.didi.nl. AAAA ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33979 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;www.didi.nl. IN AAAA
;; ANSWER SECTION: www.didi.nl. 3520 IN AAAA 2001:888:2087:33::132
;; Query time: 20 msec ;; SERVER: 2001:470:20::2#53(2001:470:20::2) ;; WHEN: Wed Jan 4 15:44:06 2012 ;; MSG SIZE rcvd: 57
And if that is already cached, let's try something that should require a fresh lookup:
(neodymium:15:44)% dig @2001:470:20::2 tengigabitethernet.com. AAAA
; <<>> DiG 9.7.3 <<>> @2001:470:20::2 tengigabitethernet.com. AAAA ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41662 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;tengigabitethernet.com. IN AAAA
;; ANSWER SECTION: tengigabitethernet.com. 3600 IN AAAA 2001:48c8:1:104::e
;; Query time: 84 msec ;; SERVER: 2001:470:20::2#53(2001:470:20::2) ;; WHEN: Wed Jan 4 15:44:41 2012 ;; MSG SIZE rcvd: 68
Again, not too bad..
- Mark
-- Mark Kamichoff prox@prolixium.com http://www.prolixium.com/