named.conf issues

[ewebza]

Hi,

I have a primary webserver which also acts as a primary nameserver, lets call it web1.
There is a VPS that runs WHM DNSOnly which acts only as a secondary nameserver, it is set up a cluster with web1, let's call it dns1.

On web1, named.conf has no options {} block @ all. I've read some other posts on this forum and I've added the following to my named.conf on web1

acl "trusted_ips" {
        213.239.x.x;
        213.239.x.x;
        127.0.0.1;
        46.4.x.x;
        46.4.x.x;
        46.4.x.x;
        78.46.x.x;
        78.46.x.x;
        78.46.x.x;
        78.46.x.x;
        78.46.x.x;
        78.46.x.x;
        78.46.x.x;
        78.46.x.x;
        198.12.x.x;
};

options {
	directory "/var/named";
#	allow-recursion { trusted_ips; };
#	allow-notify { trusted_ips; };
#	allow-transfer { trusted_ips; };
#	allow-query { trusted_ips; };
};

trusted_ips are all the IP's assigned to this box, with the last IP being the VPS (dns1)

If I uncomment the allow* lines in options {} named restarts without a problem but if I nslookup on the box (web1) it fails

[email protected] [/var/log]# nslookup google.co.za
;; connection timed out; trying next origin

Also, when this happens, none of my mail gets delivered to @google.com / @yahoo.com which I would assume is because it can't lookup the domains (web1).

Any idea how I can fix this? At the moment the NS allows remote queries and recursion which I do not want.

 

[hgrg]

check /etc/resolv.conf for resolvers...

 

[ewebza]

Thanks, I changed my resolvers to Google's resolvers and replaced the acl variables with a full list of the IP's in each case and that seemed to work.

 

[hgrg]

you are most welcome