11 Oct
2014
11 Oct
'14
2:07 a.m.
Lynwood, I tried looking up the PTR record for some of those addresses,
and all of them respond to me quickly - just milliseconds. I don't know
what tool you're using, but "dig +trace" can be helpful in determining
the lookup hierarchy that was followed and may point to where the lookups
that you're doing have failed.
Here is "dig +trace -x 44.60.44.1" from my home. Note that it returned
the answer in 41 ms, no timeout. I tried it a few times and always got
an answer quickly; the longest (240 ms) was when the last server to be
queried was Munnari across the Pacific Ocean.
- Brian
; <<>> DiG 9.7.1-P2 <<>> +trace -x 44.60.44.1
;; global options: +cmd
. 474646 IN NS c.root-servers.net.
. 474646 IN NS l.root-servers.net.
. 474646 IN NS d.root-servers.net.
. 474646 IN NS i.root-servers.net.
. 474646 IN NS e.root-servers.net.
. 474646 IN NS m.root-servers.net.
. 474646 IN NS b.root-servers.net.
. 474646 IN NS a.root-servers.net.
. 474646 IN NS j.root-servers.net.
. 474646 IN NS g.root-servers.net.
. 474646 IN NS f.root-servers.net.
. 474646 IN NS h.root-servers.net.
. 474646 IN NS k.root-servers.net.
;; Received 228 bytes from 209.18.47.61#53(209.18.47.61) in 14 ms
in-addr.arpa. 172800 IN NS e.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS c.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS d.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS f.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS a.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS b.in-addr-servers.arpa.
;; Received 417 bytes from 192.5.5.241#53(f.root-servers.net) in 24 ms
44.in-addr.arpa. 86400 IN NS munnari.oz.au.
44.in-addr.arpa. 86400 IN NS ampr-dns.in-berlin.de.
44.in-addr.arpa. 86400 IN NS ampr.org.
44.in-addr.arpa. 86400 IN NS hamradio.ucsd.edu.
44.in-addr.arpa. 86400 IN NS ns2.threshinc.com.
44.in-addr.arpa. 86400 IN NS ns0.comgw.net.
44.in-addr.arpa. 86400 IN NS ns1.defaultroute.net.
;; Received 245 bytes from 193.0.9.1#53(f.in-addr-servers.arpa) in 149 ms
1.44.60.44.in-addr.arpa. 3600 IN PTR kb3vwg-001.ampr.org.
44.in-addr.arpa. 3600 IN NS ampr-dns.in-berlin.de.
44.in-addr.arpa. 3600 IN NS ns2.threshinc.com.
44.in-addr.arpa. 3600 IN NS munnari.OZ.AU.
44.in-addr.arpa. 3600 IN NS ampr.org.
44.in-addr.arpa. 3600 IN NS hamradio.ucsd.edu.
44.in-addr.arpa. 3600 IN NS ns0.comgw.net.
44.in-addr.arpa. 3600 IN NS ns1.defaultroute.net.
;; Received 330 bytes from 192.41.222.8#53(ns2.threshinc.com) in 41 ms
On Fri, Oct 10, 2014 at 05:28:22PM -0400, lleachii(a)aol.com wrote:
I allow all to to lookup 44.in-addr.arpa and ampr.org;
and it works. BUT, some reverse records always time out.
So far, I have tested the following IP addresses which have PTR records, but do not
produce results:
44.102.1.1
44.102.1.2
44.108.1.1
44.108.1.2
44.108.1.3
44.60.44.1
44.60.44.2
44.60.44.3
44.60.44.6
44.60.44.7
The only pattern that I've discovered when a lookup times out, is that the fourth
octet is always less than 10. I've checked the system log, and there is no denial for
the DSN query. I was wondering if anyone had ideas/suggestions.