I am running my domain myself via Bind 9.2.1 on a RedHat 7.2 machine. Had been running it fine with version 8 for quite some time & still trying to get my head around the changes in version 9.

I am running bind in debug mode for the moment to iron out any problems i may be having

My secondary DNS host is easydns.com & i am seeing these errors in my log file. Can anyone explain them to me

Sep 01 19:55:43.168 xfer-out: info: client 64.39.29.212#1631: transfer of 'eziekiel.com/IN': AXFR-style IXFR started
Sep 01 19:55:43.918 xfer-out: info: client 212.100.224.80#4133: transfer of 'eziekiel.com/IN': AXFR-style IXFR started
Sep 01 19:55:54.300 notify: debug 1: zone eziekiel.com/IN: notify to 198.142.106.21#53 failed: timed out
Sep 01 19:56:09.320 notify: debug 1: zone eziekiel.com/IN: notify to 198.142.106.21#53 failed: timed out
Sep 01 19:56:24.340 notify: debug 1: zone eziekiel.com/IN: notify to 198.142.106.21#53 failed: timed out

My DNS server is actually an internal machine on a private 192.168 range IP but my firwall is portforwarding requests to port 53 to it

Regards

Andrew

Could you explein what is 198.142.106.21 for you?

Chances are you dont have FWD and RR for your internal IP. Bind 9 has rules to now allow queries on internal nets, but it needs to know FQDN who itself is (bad grammar). Setup a zone for your 192.168/24.

Yes, the above IP address is simply my static that is assigned to my connection by my ISP. The machine that gets it is my firewall

It acts as my gateway for internal machines, one of these being my DNS server (DND server is also my webserver). All machines have internal IP range of 192.168.0.*

So my DNS machine is listening on these IP addresses

tcp 0 0 192.168.0.2:53 0.0.0.0:* LISTEN 829/named

tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 829/named

udp 0 0 192.168.0.2:53 0.0.0.0:* 829/named
udp 0 0 127.0.0.1:53 0.0.0.0:* 829/named

I must not have stated it well enough then. You have to have zone information for the server and on the server. ie..a fwd entry for dns.zone.com pointing to the 192.168 address of the dns server. and then an RR zone pointing that 192.168 address back at the same dns.zone.com entry.

dns.zone.com is supposed to be replace by whatever the FQDN name of that box is.