indentical caching only name servers having problems resolving domain
majorboredum
majorboredum at yahoo.com
Fri Jan 10 16:33:52 UTC 2003
Hello;
I'm having problems resolving a particular domain name using our
caching only nameservers.
One nameserver is resolving it correctly with no errors.
<<>> DiG 9.2.1 <<>> bet1.wagermillennium.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41485
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 2
;; QUESTION SECTION:
;bet1.wagermillennium.com. IN A
;; ANSWER SECTION:
bet1.wagermillennium.com. 252774 IN A 200.9.49.37
bet1.wagermillennium.com. 252774 IN A 64.35.160.153
;; AUTHORITY SECTION:
wagermillennium.com. 16769 IN NS
nome.wagermillennium.com.
;; ADDITIONAL SECTION:
nome.wagermillennium.com. 194268 IN A 64.35.160.143
nome.wagermillennium.com. 194268 IN A 200.9.49.34
;; Query time: 26 msec
;; SERVER: x.x.x.x#53(x.x.x.x)
;; WHEN: Fri Jan 10 10:22:14 2003
;; MSG SIZE rcvd: 125
The other server encounters this:
; <<>> DiG 9.2.1 <<>> @x.x.x.x bet1.wagermillennium.com
;; global options: printcmd
;; connection timed out; no servers could be reached
We are not having issues resolving other domains on either server.
I am able to resolve this domain using 2 other name servers as well.
When trying to resolve the domain directly from the server with the
problem the following output is produced:
; <<>> DiG 8.3 <<>> bet1.wagermillennium.com
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 2
;; QUERY SECTION:
;; bet1.wagermillennium.com, type = A, class = IN
;; ANSWER SECTION:
bet1.wagermillennium.com. 2d22h5m56s IN A 200.9.49.37
bet1.wagermillennium.com. 2d22h5m56s IN A 64.35.160.153
;; AUTHORITY SECTION:
wagermillennium.com. 4h32m31s IN NS nome.wagermillennium.com.
;; ADDITIONAL SECTION:
nome.wagermillennium.com. 2d5h50m50s IN A 64.35.160.143
nome.wagermillennium.com. 2d5h50m50s IN A 200.9.49.34
;; Total query time: 5004 msec
;; FROM: x to SERVER: default -- x.x.x.x
;; WHEN: Fri Jan 10 10:29:25 2003
;; MSG SIZE sent: 42 rcvd: 125
The very long query time concerns me.
Can someone please offer me some advice on what the issue may be ?
I can try and provide more information if needed.
Sincerely
Major B
More information about the bind-users
mailing list