|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] where is phila.gov? [now caching dns problem]
|
> [...]
Wow .... so the problem is with my caching DNS server ... not so OT
anymore either :-D
I have never had a problem (I think) with any other domain, and
this server has been in place for months. Does anybody have a
clue why phila.gov would be a problem for my server? I'm using
bind 9.2.5.
My server fails:
$ dig brtweb.phila.gov @127.0.0.1
; <<>> DiG 9.2.5 <<>> brtweb.phila.gov @127.0.0.1
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
Here is a trace:
$ dig +trace +additional phila.gov @127.0.0.1
; <<>> DiG 9.2.5 <<>> +trace +additional phila.gov @127.0.0.1
; (1 server found)
;; global options: printcmd
. 187144 IN NS
F.ROOT-SERVERS.NET.
. 187144 IN NS
G.ROOT-SERVERS.NET.
. 187144 IN NS
H.ROOT-SERVERS.NET.
. 187144 IN NS
I.ROOT-SERVERS.NET.
. 187144 IN NS
J.ROOT-SERVERS.NET.
. 187144 IN NS
K.ROOT-SERVERS.NET.
. 187144 IN NS
L.ROOT-SERVERS.NET.
. 187144 IN NS
M.ROOT-SERVERS.NET.
. 187144 IN NS
A.ROOT-SERVERS.NET.
. 187144 IN NS
B.ROOT-SERVERS.NET.
. 187144 IN NS
C.ROOT-SERVERS.NET.
. 187144 IN NS
D.ROOT-SERVERS.NET.
. 187144 IN NS
E.ROOT-SERVERS.NET.
M.ROOT-SERVERS.NET. 604653 IN A 202.12.27.33
;; Received 244 bytes from 127.0.0.1#53(127.0.0.1) in 1 ms
gov. 172800 IN NS
E.GOV.ZONEEDIT.COM.
gov. 172800 IN NS
F.GOV.ZONEEDIT.COM.
gov. 172800 IN NS
G.GOV.ZONEEDIT.COM.
gov. 172800 IN NS
A.GOV.ZONEEDIT.COM.
gov. 172800 IN NS
B.GOV.ZONEEDIT.COM.
gov. 172800 IN NS
C.GOV.ZONEEDIT.COM.
gov. 172800 IN NS
D.GOV.ZONEEDIT.COM.
A.GOV.ZONEEDIT.COM. 172800 IN A 216.55.155.29
B.GOV.ZONEEDIT.COM. 172800 IN A 206.51.224.229
C.GOV.ZONEEDIT.COM. 172800 IN A 69.72.142.35
D.GOV.ZONEEDIT.COM. 172800 IN A 209.97.207.48
E.GOV.ZONEEDIT.COM. 172800 IN A 82.165.40.134
F.GOV.ZONEEDIT.COM. 172800 IN A 66.197.185.229
G.GOV.ZONEEDIT.COM. 172800 IN A 66.135.32.100
;; Received 267 bytes from 192.5.5.241#53(F.ROOT-SERVERS.NET) in
93 ms
phila.gov. 86400 IN NS DNS.phila.gov.
phila.gov. 86400 IN NS DNS2.phila.gov.
DNS.phila.gov. 86400 IN A 170.115.249.10
DNS2.phila.gov. 86400 IN A 170.115.249.11
;; Received 96 bytes from 82.165.40.134#53(E.GOV.ZONEEDIT.COM) in
168 ms
;; Received 27 bytes from 170.115.249.10#53(DNS.phila.gov) in 0
ms
Passing in the real IP number of their dns server gives me the correct
result:
$ dig +norec +noques +nostats +nocmd brtweb.phila.gov @170.115.249.10
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31400
;; flags: qr aa ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; ANSWER SECTION:
brtweb.phila.gov. 86400 IN A 170.115.249.40
;; AUTHORITY SECTION:
phila.gov. 86400 IN NS dns2.phila.gov.
phila.gov. 86400 IN NS dns.phila.gov.
;; ADDITIONAL SECTION:
dns2.phila.gov. 86400 IN A 170.115.249.11
dns.phila.gov. 86400 IN A 170.115.249.10
Is this what my caching dns server attempts to ask for?:
$ dig +norec +noques +nostats +nocmd brtweb.phila.gov @dns.phila.gov
dig: couldn't get address for 'dns.phila.gov': failure
Could this be my problem?
$ whois phila.gov
Timeout.
Any help is appreciated, thanks.
--
Chris Cera http://cera.us
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|