SOLVED-
--------------------------------------------------------
My resolv.conf was point to my local server but named is not recursive. set to allow localhost recursion and did the trick.
http://www.directadmin.com/forum/showthread.php?s=&postid=71544#post69855
--------------------------------------------------------
Hi,
I've been having issues lately with my DA VPS server. DA has always worked fine for me in the past and all hostnames can be resolved by my server. But 3-4 days ago, the problem started where no hostnames can be resolved.
My resolv.conf is set to use 2 ip addresses which belongs to the server. So effectively I'm using DA's named to resolve hostnames.
Unfortunately I'm not too familiar with DNS and named before, I've been doing continuous read-ups on it. My question is though however, if I'm using my localhost's named to resolve all kind of hostnames how does my localhost's named service get this information from? - if I cannot ping or dig any domains such as google.com?
The only significant thing happened in the past 3-4 days was my VPS provider moved the machine to a different DC.
dig google.com returns:
--------
In my named.conf this line is commented out:
// query-source address * port 53;
My VPS is running CentOS5 with APF firewall, my firewall rules has allowed port 53 to remain open, but should I uncomment that line? Does that then forces all DNS queries through 53 rather than a random port which maybe the problem here?? (although I can't understand why it worked for the last 6 months but stopped working a couple of days ago)
--------------------------------------------------------
My resolv.conf was point to my local server but named is not recursive. set to allow localhost recursion and did the trick.
http://www.directadmin.com/forum/showthread.php?s=&postid=71544#post69855
--------------------------------------------------------
Hi,
I've been having issues lately with my DA VPS server. DA has always worked fine for me in the past and all hostnames can be resolved by my server. But 3-4 days ago, the problem started where no hostnames can be resolved.
My resolv.conf is set to use 2 ip addresses which belongs to the server. So effectively I'm using DA's named to resolve hostnames.
Unfortunately I'm not too familiar with DNS and named before, I've been doing continuous read-ups on it. My question is though however, if I'm using my localhost's named to resolve all kind of hostnames how does my localhost's named service get this information from? - if I cannot ping or dig any domains such as google.com?
The only significant thing happened in the past 3-4 days was my VPS provider moved the machine to a different DC.
dig google.com returns:
--------
Code:
; <<>> DiG 9.3.3rc2 <<>> google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59742
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com. IN A
;; AUTHORITY SECTION:
. 3600000 IN NS B.ROOT-SERVERS.NET.
. 3600000 IN NS C.ROOT-SERVERS.NET.
. 3600000 IN NS D.ROOT-SERVERS.NET.
. 3600000 IN NS E.ROOT-SERVERS.NET.
. 3600000 IN NS F.ROOT-SERVERS.NET.
. 3600000 IN NS G.ROOT-SERVERS.NET.
. 3600000 IN NS H.ROOT-SERVERS.NET.
. 3600000 IN NS I.ROOT-SERVERS.NET.
. 3600000 IN NS J.ROOT-SERVERS.NET.
. 3600000 IN NS K.ROOT-SERVERS.NET.
. 3600000 IN NS L.ROOT-SERVERS.NET.
. 3600000 IN NS M.ROOT-SERVERS.NET.
. 3600000 IN NS A.ROOT-SERVERS.NET.
;; Query time: 0 msec
;; SERVER: 85.234.147.6#53(85.234.147.6)
;; WHEN: Sat Apr 19 20:39:55 2008
;; MSG SIZE rcvd: 239
Code:
nslookup google.com
;; Got referral reply from 85.234.147.6, trying next server
Server: 85.234.147.7
Address: 85.234.147.7#53
Non-authoritative answer:
*** Can't find google.com: No answerIn my named.conf this line is commented out:
// query-source address * port 53;
My VPS is running CentOS5 with APF firewall, my firewall rules has allowed port 53 to remain open, but should I uncomment that line? Does that then forces all DNS queries through 53 rather than a random port which maybe the problem here?? (although I can't understand why it worked for the last 6 months but stopped working a couple of days ago)
Last edited: