I've just noticed that on my new server (ns5.cdbsystems.com) though named is running and I followed the install-chroot-bind howto, I cant get to it from outside world.
when I do
dig @ns5.cdbsystems.com cdbsystems.com
I get REFUSED form dig.
my other nameserver
dig @ns4.cdbsystems.com cdbsystems.com
reponds normally.
how can I tell what named is up to?
one complicating factor is I have it behind a xincom dual-wan router.
The centos 5.1 server has a static ip of 192.168.2.50 and I have
the router passing through all dns / port 53 request (tcp and udp) to this static ip.
the router ip is 71.163.161.26 which is of course what ns5.cdbsystems.com is saved as at godaddy (the registrar) and ns4.cdbsystems.com.
doing /etc/rc.d/rc3.d/S13named restart messages contains:
May 14 13:50:29 ns5 named[1999]: shutting down: flushing changes
May 14 13:50:29 ns5 named[1999]: stopping command channel on 127.0.0.1#953
May 14 13:50:29 ns5 named[1999]: stopping command channel on ::1#953
May 14 13:50:29 ns5 named[1999]: no longer listening on 127.0.0.1#53
May 14 13:50:29 ns5 named[1999]: no longer listening on 192.168.2.50#53
May 14 13:50:29 ns5 named[1999]: exiting
May 14 13:50:31 ns5 named[3456]: starting BIND 9.3.3rc2 -u named -t /var/named/chroot
May 14 13:50:31 ns5 named[3456]: found 2 CPUs, using 2 worker threads
May 14 13:50:31 ns5 named[3456]: loading configuration from '/etc/named.conf'
May 14 13:50:31 ns5 named[3456]: listening on IPv4 interface lo, 127.0.0.1#53
May 14 13:50:31 ns5 named[3456]: listening on IPv4 interface eth0, 192.168.2.50#53
May 14 13:50:31 ns5 named[3456]: command channel listening on 127.0.0.1#953
May 14 13:50:31 ns5 named[3456]: command channel listening on ::1#953
May 14 13:50:31 ns5 named[3456]: zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42
May 14 13:50:31 ns5 named[3456]: zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700
May 14 13:50:31 ns5 named[3456]: zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42
May 14 13:50:31 ns5 named[3456]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0.0.ip6.arpa/IN/localhost_resolver: loaded serial 1997022700
May 14 13:50:31 ns5 named[3456]: zone localdomain/IN/localhost_resolver: loaded serial 42
May 14 13:50:31 ns5 named[3456]: zone localhost/IN/localhost_resolver: loaded serial 1
May 14 13:50:31 ns5 named[3456]: zone cdbsystems.com/IN/external: loaded serial 1997022735
May 14 13:50:31 ns5 named[3456]: zone cdbsystems.com/IN/external: sending notifies (serial 1997022735)
May 14 13:50:31 ns5 named[3456]: running
May 14 13:50:31 ns5 named[3456]: client 192.168.2.1#1345: view internal: received notify for zone 'cdbsystems.com': not authoritative
on ns4.cdbsystems.com (and ns5) the cdbsystems.hosts file contains:
-------------------------------------
$TTL 84600
@ IN SOA cdbsystems.com. root.cdbsystems.com. (
1997022735 ; Serial
3600 ; Refresh
14400 ; Retry
1209600 ; Expire
86400 ) ; TTL
IN NS ns4.cdbsystems.com.
IN NS ns5.cdbsystems.com.
admin IN A 65.254.36.202
ns6 IN A 65.254.36.202
newbrutha IN A 65.254.36.202
cdbtest IN A 65.254.36.202
inthezoneonline IN A 65.254.36.202
ns5 IN A 71.163.161.26
ns4 IN A 65.254.36.202
www IN A 71.163.161.26
ns3 IN A 65.254.36.202
ns2 IN A 65.254.36.202
www2 IN A 65.254.36.202
ns1 IN CNAME admin
wwwns5 IN CNAME admin
ftp IN CNAME admin
pop3 IN CNAME admin
smtp IN CNAME admin
mail IN CNAME admin
cdbsystems.com. MX 50 ns4.cdbsystems.com.
-----------------
any ideas as to how to diagnose the problem?
I notice in messages reference to ports 953 and 1345 as far as I know the firewall is NOT passing those through - do I need to allow them?
(most firewall setup howtos only mention 53 and making sure TCP and UDP are both allowed for DNS passthrough)
any help is most welcome
cdb.
Recent comments
16 hours 53 sec ago
18 hours 56 min ago
20 hours 10 min ago
21 hours 33 min ago
23 hours 11 min ago
1 day 40 min ago
1 day 1 hour ago
1 day 17 hours ago
1 day 18 hours ago
1 day 22 hours ago