DNS problems
Hi all,
I am having some problems with my DNS properly resolving; I have a domain with namecheap, I have ns1 propogated to 68.64.169.81, and ns2 to 68.64.169.82.
Now, when I try to resolve my domain I get a server timeout.
When I dig the domain using the 4.2.2.2 resolver I get;
However, when I dig at my own local nameserver;
So I am very confused, to me it seems like it is getting lost somewhere in chain of servers. Any thought on this? Thanks!
root@octane [~]# nslookup xendev.net. 4.2.2.2
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached
When I dig the domain using the 4.2.2.2 resolver I get;
root@octane [~]# dig @4.2.2.2 xendev.net
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.6 <<>> @4.2.2.2 xendev.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 60756
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;xendev.net. IN A
;; Query time: 0 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Wed Dec 4 17:20:29 2013
;; MSG SIZE rcvd: 28
However, when I dig at my own local nameserver;
root@octane [~]# dig @68.64.169.81 xendev.net
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.6 <<>> @68.64.169.81 xendev.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18041
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;xendev.net. IN A
;; ANSWER SECTION:
xendev.net. 14400 IN A 68.64.169.90
;; AUTHORITY SECTION:
xendev.net. 86400 IN NS ns2.xendev.net.
xendev.net. 86400 IN NS ns1.xendev.net.
;; ADDITIONAL SECTION:
ns1.xendev.net. 14400 IN A 68.64.169.81
ns2.xendev.net. 14400 IN A 68.64.169.82
;; Query time: 0 msec
;; SERVER: 68.64.169.81#53(68.64.169.81)
;; WHEN: Wed Dec 4 17:21:17 2013
;; MSG SIZE rcvd: 112
So I am very confused, to me it seems like it is getting lost somewhere in chain of servers. Any thought on this? Thanks!
-
Hello :) Have you tried temporarily disabling your firewall rules to rule that out as the cause of the problem? Also, you may want to try rebuilding the DNS configuration to see if that helps. EX: mv /etc/named.conf /etc/named.conf.backup /scripts/rebuilddnsconfig
If the issue continues, it be worth re-creating the DNS Zone associated with the domain name to ensure it's not corrupted. Thank you.0
Please sign in to leave a comment.
Comments
1 comment