We run two Debian Squeeze servers with Bind9 running to provide public DNS to our services. I'm having an odd problem with lookups and I'm not sure what I should do to fix it.
ns-uk-1 is on x.y.z.60 and is the slave.
ns-uk-2 is on x.y.z.59 and is the master.
x.y.z is a public IP address. Both servers also have private addresses.
Zone transfers from master to slave are working, and changes made on the master are reflected on the slave.
If I run nslookup from my Windows PC and set the nameserver to ns-uk-2 I can run lookups just fine. Setting the server to ns-uk-1 and performing the same lookups just gives me timeout messages.
I have setup a slave Windows public DNS server (ns3) on x.y.z.61 and lookups from that also work fine, so there must be some odd configuration issue that's causing ns-uk-1 to timeout.
In addition, I can't get reverse lookups to work either. I have created the appropriate zone files, and if I run a reverse lookup from my PC against ns-uk-2 or ns3 then I get the expected result. ns-uk-1 just times out.
Running reverse lookups from somewhere like mxtoolbox I either get timeout errors or 'loop detected' errors.
I'm not sure which config files you might want to nosey at, so here's a selection:
The external part of /etc/bind/named.conf
Code:
# Publicly accessible DNS
#
view "internet" {
# This view applies to all the other machines
match-clients { any; };
allow-query { any; };
allow-transfer { 62.232.156.60; 62.232.156.61; };
notify yes;
also-notify { 62.232.156.60; 62.232.156.61; };
recursion no;
additional-from-cache no;
# additional-from-auth no;
include "master/named.conf.zones";
include "master/named.conf.default.zones";
};
include "/etc/bind/rndc.key";
/var/lib/named/master/named.conf.zones
Code:
zone "156.232.62.in-addr.arpa" IN {
type master;
file "master/156.232.62.in-addr.arpa";
allow-update { none; };
};
zone "aminocom.com" IN {
type master;
file "master/aminocom.com";
allow-update { none; };
};
Part of /var/lib/named/master/aminocom.com
Code:
; Public DNS zone file for aminocom.com
$TTL 1d;
@ IN SOA ns-uk-1.aminocom.com. it.aminocom.com. (
2013040906 ; today's date and serial number
28800 ; Refresh
7200 ; Retry
259200 ; Expire in 1 days
10800) ; Minimum
IN NS ns-uk-1.aminocom.com.
IN NS ns-uk-2.aminocom.com.
IN NS ns3.aminocom.com.
IN MX 10 mx-swa-1.aminocom.com.
IN MX 20 mx-swa-2.aminocom.com.
ns-uk-1 IN A 62.232.156.60
ns-uk-2 IN A 62.232.156.59
ns3 IN A 62.232.156.61
download IN A 62.232.156.58
ftp IN CNAME download
/var/lib/named/master/156.232.62.in-addr.arpa
Code:
$TTL 1d;
@ IN SOA aminocom.com. it.aminocom.com. (
2013040902 ; today's date and serial number
28800 ; Refresh
7200 ; Retry
259200 ; Expire in 1 days
10800) ; Minimum
IN NS ns-uk-1.aminocom.com.
IN NS ns-uk-2.aminocom.com.
IN NS ns3.aminocom.com.
59 IN PTR mail2.aminocom.com.
60 IN PTR mail.aminocom.com.
Sorry for the wall of text, but I've been looking at this for a few days now, and I can't see anything obviously wrong. I suspect I've gone number blind though!
