[171520] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Paging HP DNS admin

daemon@ATHENA.MIT.EDU (Chris Adams)
Sat May 3 23:14:00 2014

X-Original-To: nanog@nanog.org
Date: Sat, 3 May 2014 22:13:51 -0500
From: Chris Adams <cma@cmadams.net>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <CAL9jLaYvjacMKGZgt95ty3PBJzwT=uyb_5HZwEnPSxn5HXhuew@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org

Once upon a time, Christopher Morrow <morrowc.lists@gmail.com> said:
> if I ask ns1/2/3/4/5/6.hp.com directly for AAAA for onramp01.hpeprint.com.:
> 
> ; <<>> DiG 9.8.1-P1 <<>> AAAA onramp01.hpeprint.com. @ns6.hp.com
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30318
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 6
> ;; WARNING: recursion requested but not available
> 
> ;; QUESTION SECTION:
> ;onramp01.hpeprint.com.         IN      AAAA

You left out the authority section that refers you to the correct DNS
servers - ns[1-6].hp.com are not it.  They delegate to another set of HP
servers, which all time out (as stated by the OP) when asked for AAAA.

Oddly, it seems to be specific to AAAA; any other type request I send
comes back NOERROR correctly.  It is like somebody tried to handle AAAA
"special" and screwed it up.

-- 
Chris Adams <cma@cmadams.net>

home help back first fref pref prev next nref lref last post