BIND works internally, refused externally, on VPS name server

steve willett · 07-05-2011, 07:31 PM

I did not install bind - this is a VPS server and it was already installed. All I did was to request that the service be activated through the Container Management Panel. I am not familiar with running "chrooted", but I moved my named.conf file to the path specified and reloaded named. Now it no longer works internally:
[root@s15495435 etc]# dig yoursportsleague.com @ns2.yoursportsleague.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> yoursportsleague.com @ns2.yoursportsleague.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 61319
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;yoursportsleague.com. IN A

;; Query time: 18 msec
;; SERVER: 74.208.234.121#53(74.208.234.121)
;; WHEN: Tue Jul 5 19:27:05 2011
;; MSG SIZE rcvd: 38

Is this progress?

bathory · 07-06-2011, 03:21 AM

Hi,

Code:

I am not familiar with running "chrooted", but I moved my named.conf file to the path specified and reloaded named. Now it no longer works internally:

You have to move it into the jail, but need to create a symlink in /etc/named.conf since you're using "-c /etc/named.conf" in the startup options.