Unable to resolve reillycompany.com except with +trace
Joel M Nimety
jnimety at perimeterco.com
Tue Jan 11 19:17:37 UTC 2005
OK, here is a trace and the relevenat portions of a cache dump. I don;t
know enough to tell if anything looks out of place.
trace:
11-Jan-2005 13:28:23.980 client 10.25.5.200#32772: view internal-in:
query (cache) 'oreillycompany.com/A/IN' approved
11-Jan-2005 13:28:23.980 createfetch: oreillycompany.com A
11-Jan-2005 13:28:23.980 fctx 0x2cb6b8(oreillycompany.com/A'): create
11-Jan-2005 13:28:23.980 fctx 0x2cb6b8(oreillycompany.com/A'): join
11-Jan-2005 13:28:23.980 fetch 0x314218 (fctx
0x2cb6b8(oreillycompany.com/A)): created
11-Jan-2005 13:28:23.981 fctx 0x2cb6b8(oreillycompany.com/A'): start
11-Jan-2005 13:28:23.981 fctx 0x2cb6b8(oreillycompany.com/A'): try
11-Jan-2005 13:28:23.981 fctx 0x2cb6b8(oreillycompany.com/A'): cancelqueries
11-Jan-2005 13:28:23.981 fctx 0x2cb6b8(oreillycompany.com/A'): getaddresses
11-Jan-2005 13:28:23.981 fctx 0x2cb6b8(oreillycompany.com/A'): query
11-Jan-2005 13:28:23.981 resquery 0x3096b8 (fctx
0x2cb6b8(oreillycompany.com/A)): send
11-Jan-2005 13:28:23.982 resquery 0x3096b8 (fctx
0x2cb6b8(oreillycompany.com/A)): sent
11-Jan-2005 13:28:23.982 resquery 0x3096b8 (fctx
0x2cb6b8(oreillycompany.com/A)): senddone
11-Jan-2005 13:28:24.061 resquery 0x3096b8 (fctx
0x2cb6b8(oreillycompany.com/A)): response
11-Jan-2005 13:28:24.061 fctx 0x2cb6b8(oreillycompany.com/A'):
noanswer_response
11-Jan-2005 13:28:24.061 fctx 0x2cb6b8(oreillycompany.com/A'):
ncache_message
11-Jan-2005 13:28:24.062 fctx 0x2cb6b8(oreillycompany.com/A'): clone_results
11-Jan-2005 13:28:24.062 fctx 0x2cb6b8(oreillycompany.com/A'): cancelquery
11-Jan-2005 13:28:24.062 fctx 0x2cb6b8(oreillycompany.com/A'): done
11-Jan-2005 13:28:24.062 fctx 0x2cb6b8(oreillycompany.com/A'):
stopeverything
11-Jan-2005 13:28:24.062 fctx 0x2cb6b8(oreillycompany.com/A'): cancelqueries
11-Jan-2005 13:28:24.062 fctx 0x2cb6b8(oreillycompany.com/A'): sendevents
11-Jan-2005 13:28:24.062 fetch 0x314218 (fctx
0x2cb6b8(oreillycompany.com/A)): destroyfetch
11-Jan-2005 13:28:24.062 fctx 0x2cb6b8(oreillycompany.com/A'): shutdown
11-Jan-2005 13:28:24.063 fctx 0x2cb6b8(oreillycompany.com/A'): doshutdown
11-Jan-2005 13:28:24.063 fctx 0x2cb6b8(oreillycompany.com/A'):
stopeverything
11-Jan-2005 13:28:24.063 fctx 0x2cb6b8(oreillycompany.com/A'): cancelqueries
11-Jan-2005 13:28:24.063 fctx 0x2cb6b8(oreillycompany.com/A'): destroy
cache dump:
; glue
reillycompany.com. 171459 NS ns1.infostations.net.
171459 NS ns2.infostations.net.
; authauthority
infostations.NET. 1400 NS ns1.bluecherry.net.
1400 NS ns1.infostations.net.
1400 NS ns2.bluecherry.net.
1400 NS ns2.infostations.net.
; authanswer
1400 A 71.4.42.2
; answer
ns1.infostations.NET. 170546 A 71.4.40.3
; additional
ns2.infostations.NET. 1400 A 71.4.40.4
Joel M Nimety wrote:
> Additional query with +norecurse that may be helpful:
>
> [jnimety at jnimety-linux ~]$ dig @ns77 reillycompany.com +norecurse
>
> ; <<>> DiG 9.2.4 <<>> @ns77 reillycompany.com +norecurse
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45998
> ;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
>
> ;; QUESTION SECTION:
> ;reillycompany.com. IN A
>
> ;; AUTHORITY SECTION:
> reillycompany.com. 172783 IN NS ns1.infostations.net.
> reillycompany.com. 172783 IN NS ns2.infostations.net.
>
> ;; ADDITIONAL SECTION:
> ns1.infostations.net. 172783 IN A 71.4.40.3
> ns2.infostations.net. 172783 IN A 71.4.40.4
>
> ;; Query time: 5 msec
> ;; SERVER: 10.25.1.77#53(ns77)
> ;; WHEN: Tue Jan 11 11:07:26 2005
> ;; MSG SIZE rcvd: 119
>
> [jnimety at jnimety-linux ~]$
>
> Stephane Bortzmeyer wrote:
>
>>On Tue, Jan 11, 2005 at 09:24:21AM -0500,
>> Joel M Nimety <jnimety at perimeterco.com> wrote
>> a message of 33 lines which said:
>>
>>
>>
>>>no, resolv.conf:
>>>
>>>nameserver 127.0.0.1
>>
>>
>>So what? It is not less a name server / cache / forwarder just because
>>it is listening on the loopback interface.
>
>
--
Joel Nimety
Perimeter Internetworking Corp.
203.331.4416
------------------------------------------------------------------------
This e-mail transmission may contain information that is proprietary,
privileged and/or confidential and is intended exclusively for the
person(s) to whom it is addressed. Any use, copying, retention or
disclosure by any person other than the intended recipient or the
intended recipient's designees is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
return e-mail and delete all copies.
More information about the bind-users
mailing list