not listening on tcp

Maria Iano maria at iano.org
Mon May 23 16:35:30 UTC 2005


Sorry - no there was nothing mentioned at all in the log file. Just now I turned debugging up to level 9 and restarted it. After the first restart, it was not listening on tcp port 53. I restarted again, and it was listening on tcp port 53. As before, at all times it does listen on udp port 53. It really does seem to just alternate whether or not it listens to tcp. There was nothing to explain it in the log file that I could see.

This name server just does resolution for our external clients and servers as well as for some forwarding Bind servers inside our firewalls. To prevent them from forwarding RFC 1918 queries to the roots I have configured dummy zones for them, and you can see in the logs when they get loaded. We have a small RFC 1918 ( 25.111.10.in-addr.arpa) that some outside servers do unfortunately need to resolve. I have that configured with a very tight access list so that only those few servers that need it can resolve it. I have 3 other name servers that perform the exact same functions as this one. They pull 25.111.10.in-addr.arpa as slaves. They stopped being able to refresh that zone once this server stopped listening on tcp.

I have pasted a contiguous section from my log files below. Due to company policy I have had to replace the IP addresses of the 4 resolving name servers as I described them above. I have replaced the IP address for this name server with A.A.A.A. I have replaced the IP addresses for the other three with B.B.B.B, C.C.C.C,and D.D.D.D. It shows two restarts on 12 May, and as I said, it alternates between each restart whether or not it listens on tcp port 53. You can see the restart where it DID listen just below, because all the slaves immediately refreshed that zone I mentioned. Then you can see the two restarts from today, and the first one came up without tcp port 53 listening, and the second came up with tcp port 53 listening. I can't see anything in the log file to explain it. If any one else can I would really appreciate the help.

12-May-2005 16:18:00.510 general: info: shutting down: flushing changes
12-May-2005 16:18:00.510 general: notice: stopping command channel on 0.0.0.0#953
12-May-2005 16:18:00.510 network: info: no longer listening on 127.0.0.1#53
12-May-2005 16:18:00.510 network: info: no longer listening on A.A.A.A#53
12-May-2005 16:18:00.582 general: info: zone 10.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.583 general: info: zone 25.111.10.in-addr.arpa/IN: loaded serial 2005050501
12-May-2005 16:18:00.583 general: info: zone 0.0.127.in-addr.arpa/IN: loaded serial 2002042302
12-May-2005 16:18:00.584 general: info: zone 16.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.584 general: info: zone 17.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.585 general: info: zone 18.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.585 general: info: zone 19.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.586 general: info: zone 20.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.586 general: info: zone 21.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.586 general: info: zone 22.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.587 general: info: zone 23.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.587 general: info: zone 24.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.588 general: info: zone 25.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.588 general: info: zone 26.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.588 general: info: zone 27.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.589 general: info: zone 28.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.589 general: info: zone 29.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.590 general: info: zone 30.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.590 general: info: zone 31.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.590 general: info: zone 168.192.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:00.591 general: notice: running
12-May-2005 16:18:00.922 general: notice: exiting
12-May-2005 16:18:41.404 general: info: shutting down: flushing changes
12-May-2005 16:18:41.404 general: notice: stopping command channel on 0.0.0.0#953
12-May-2005 16:18:41.404 network: info: no longer listening on 127.0.0.1#53
12-May-2005 16:18:41.404 network: info: no longer listening on A.A.A.A#53
12-May-2005 16:18:41.439 general: notice: exiting
12-May-2005 16:18:41.467 general: info: zone 10.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.467 general: info: zone 25.111.10.in-addr.arpa/IN: loaded serial 2005050501
12-May-2005 16:18:41.468 general: info: zone 0.0.127.in-addr.arpa/IN: loaded serial 2002042302
12-May-2005 16:18:41.468 general: info: zone 16.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.469 general: info: zone 17.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.469 general: info: zone 18.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.469 general: info: zone 19.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.470 general: info: zone 20.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.470 general: info: zone 21.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.470 general: info: zone 22.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.471 general: info: zone 23.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.471 general: info: zone 24.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.472 general: info: zone 25.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.472 general: info: zone 26.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.472 general: info: zone 27.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.473 general: info: zone 28.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.473 general: info: zone 29.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.474 general: info: zone 30.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.474 general: info: zone 31.172.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.474 general: info: zone 168.192.in-addr.arpa/IN: loaded serial 2004090901
12-May-2005 16:18:41.475 general: notice: running
12-May-2005 16:18:52.557 dispatch: info: dispatch 0x83e74c0: shutting down due to TCP receive error: <unknown address, family 48830>: connection reset
12-May-2005 16:18:54.829 dispatch: info: dispatch 0x83e74c0: shutting down due to TCP receive error: <unknown address, family 48830>: connection reset
12-May-2005 16:19:03.201 dispatch: info: dispatch 0x83e74c0: shutting down due to TCP receive error: <unknown address, family 48830>: connection reset
12-May-2005 16:58:55.710 general: info: loading configuration from '/etc/named.conf'
12-May-2005 16:58:55.713 network: info: no IPv6 interfaces found
12-May-2005 16:58:55.718 general: info: zone 25.111.10.in-addr.arpa/IN: loaded serial 2005051201
12-May-2005 17:00:11.730 xfer-out: info: client B.B.B.B#59278: transfer of '25.111.10.in-addr.arpa/IN': AXFR-style IXFR started
12-May-2005 17:00:11.731 xfer-out: info: client B.B.B.B#59278: transfer of '25.111.10.in-addr.arpa/IN': AXFR-style IXFR ended
12-May-2005 17:00:31.648 xfer-out: info: client C.C.C.C#37632: transfer of '25.111.10.in-addr.arpa/IN': AXFR-style IXFR started
12-May-2005 17:00:31.648 xfer-out: info: client C.C.C.C#37632: transfer of '25.111.10.in-addr.arpa/IN': AXFR-style IXFR ended
12-May-2005 17:00:35.730 xfer-out: info: client D.D.D.D#42585: transfer of '25.111.10.in-addr.arpa/IN': AXFR-style IXFR started
12-May-2005 17:00:35.731 xfer-out: info: client D.D.D.D#42585: transfer of '25.111.10.in-addr.arpa/IN': AXFR-style IXFR ended
12-May-2005 21:03:21.026 dispatch: info: dispatch 0x83e74c0: shutting down due to TCP receive error: 64.74.96.242#53: connection reset
13-May-2005 00:46:59.622 dispatch: info: dispatch 0x83e74c0: shutting down due to TCP receive error: 65.200.162.3#53: connection reset
23-May-2005 11:43:35.131 general: info: shutting down: flushing changes
23-May-2005 11:43:35.132 general: notice: stopping command channel on 0.0.0.0#953
23-May-2005 11:43:35.132 network: info: no longer listening on 127.0.0.1#53
23-May-2005 11:43:35.132 network: info: no longer listening on A.A.A.A#53
23-May-2005 11:43:35.209 general: debug 1: now using logging configuration from config file
23-May-2005 11:43:35.209 general: debug 1: load_configuration: success
23-May-2005 11:43:35.210 general: debug 1: zone 10.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.210 general: debug 2: zone 10.in-addr.arpa/IN: number of nodes in database: 2
23-May-2005 11:43:35.210 general: debug 1: zone 10.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.210 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.210 general: debug 1: zone 10.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.210 general: info: zone 10.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.210 general: debug 1: zone 25.111.10.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.211 general: debug 2: zone 25.111.10.in-addr.arpa/IN: number of nodes in database: 7
23-May-2005 11:43:35.211 general: debug 1: zone 25.111.10.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.211 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.211 general: debug 1: zone 25.111.10.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.211 general: info: zone 25.111.10.in-addr.arpa/IN: loaded serial 2005051201
23-May-2005 11:43:35.211 general: debug 1: zone 0.0.127.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.211 general: debug 2: zone 0.0.127.in-addr.arpa/IN: number of nodes in database: 2
23-May-2005 11:43:35.211 general: debug 1: zone 0.0.127.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.211 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.211 general: debug 1: zone 0.0.127.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.211 general: info: zone 0.0.127.in-addr.arpa/IN: loaded serial 2002042302
23-May-2005 11:43:35.212 general: debug 1: zone 16.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.212 general: debug 2: zone 16.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.212 general: debug 1: zone 16.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.212 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.212 general: debug 1: zone 16.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.212 general: info: zone 16.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.212 general: debug 1: zone 17.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.212 general: debug 2: zone 17.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.212 general: debug 1: zone 17.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.212 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.212 general: debug 1: zone 17.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.212 general: info: zone 17.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.213 general: debug 1: zone 18.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.213 general: debug 2: zone 18.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.213 general: debug 1: zone 18.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.213 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.213 general: debug 1: zone 18.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.213 general: info: zone 18.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.213 general: debug 1: zone 19.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.213 general: debug 2: zone 19.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.213 general: debug 1: zone 19.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.213 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.213 general: debug 1: zone 19.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.214 general: info: zone 19.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.214 general: debug 1: zone 20.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.214 general: debug 2: zone 20.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.214 general: debug 1: zone 20.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.214 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.214 general: debug 1: zone 20.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.214 general: info: zone 20.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.214 general: debug 1: zone 21.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.214 general: debug 2: zone 21.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.214 general: debug 1: zone 21.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.214 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.214 general: debug 1: zone 21.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.214 general: info: zone 21.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.215 general: debug 1: zone 22.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.215 general: debug 2: zone 22.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.215 general: debug 1: zone 22.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.215 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.215 general: debug 1: zone 22.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.215 general: info: zone 22.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.215 general: debug 1: zone 23.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.215 general: debug 2: zone 23.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.215 general: debug 1: zone 23.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.215 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.215 general: debug 1: zone 23.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.215 general: info: zone 23.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.215 general: debug 1: zone 24.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.216 general: debug 2: zone 24.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.216 general: debug 1: zone 24.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.216 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.216 general: debug 1: zone 24.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.216 general: info: zone 24.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.216 general: debug 1: zone 25.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.216 general: debug 2: zone 25.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.216 general: debug 1: zone 25.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.216 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.216 general: debug 1: zone 25.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.216 general: info: zone 25.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.216 general: debug 1: zone 26.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.217 general: debug 2: zone 26.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.217 general: debug 1: zone 26.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.217 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.217 general: debug 1: zone 26.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.217 general: info: zone 26.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.217 general: debug 1: zone 27.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.217 general: debug 2: zone 27.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.217 general: debug 1: zone 27.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.217 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.217 general: debug 1: zone 27.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.217 general: info: zone 27.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.217 general: debug 1: zone 28.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.218 general: debug 2: zone 28.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.218 general: debug 1: zone 28.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.218 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.218 general: debug 1: zone 28.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.218 general: info: zone 28.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.218 general: debug 1: zone 29.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.218 general: debug 2: zone 29.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.218 general: debug 1: zone 29.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.218 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.218 general: debug 1: zone 29.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.218 general: info: zone 29.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.218 general: debug 1: zone 30.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.219 general: debug 2: zone 30.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.219 general: debug 1: zone 30.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.219 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.219 general: debug 1: zone 30.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.219 general: info: zone 30.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.219 general: debug 1: zone 31.172.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.241 general: debug 2: zone 31.172.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.241 general: debug 1: zone 31.172.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.241 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.241 general: debug 1: zone 31.172.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.242 general: info: zone 31.172.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.242 general: debug 1: zone 168.192.in-addr.arpa/IN: starting load
23-May-2005 11:43:35.242 general: debug 2: zone 168.192.in-addr.arpa/IN: number of nodes in database: 1
23-May-2005 11:43:35.242 general: debug 1: zone 168.192.in-addr.arpa/IN: loaded
23-May-2005 11:43:35.242 general: debug 3: no journal file, but that's OK
23-May-2005 11:43:35.242 general: debug 1: zone 168.192.in-addr.arpa/IN: journal rollforward completed successfully: no journal
23-May-2005 11:43:35.242 general: info: zone 168.192.in-addr.arpa/IN: loaded serial 2004090901
23-May-2005 11:43:35.242 general: debug 1: zone authors.bind/CH: starting load
23-May-2005 11:43:35.242 general: debug 2: zone authors.bind/CH: number of nodes in database: 0
23-May-2005 11:43:35.242 general: debug 1: zone authors.bind/CH: loaded
23-May-2005 11:43:35.242 general: debug 1: zone hostname.bind/CH: starting load
23-May-2005 11:43:35.242 general: debug 2: zone hostname.bind/CH: number of nodes in database: 0
23-May-2005 11:43:35.242 general: debug 1: zone hostname.bind/CH: loaded
23-May-2005 11:43:35.242 general: debug 1: zone version.bind/CH: starting load
23-May-2005 11:43:35.242 general: debug 2: zone version.bind/CH: number of nodes in database: 0
23-May-2005 11:43:35.242 general: debug 1: zone version.bind/CH: loaded
23-May-2005 11:43:35.242 general: debug 1: zone id.server/CH: starting load
23-May-2005 11:43:35.243 general: debug 2: zone id.server/CH: number of nodes in database: 0
23-May-2005 11:43:35.243 general: debug 1: zone id.server/CH: loaded
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 0.0.127.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 25.111.10.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 10.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 16.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 17.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 18.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 19.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 20.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 21.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 22.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 23.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 24.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 25.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 26.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 27.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 28.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 29.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 30.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 31.172.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone 168.192.in-addr.arpa/IN: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone version.bind/CH: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone hostname.bind/CH: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone authors.bind/CH: enter
23-May-2005 11:43:35.243 general: debug 1: dns_zone_maintenance: zone id.server/CH: enter
23-May-2005 11:43:35.243 general: notice: running
23-May-2005 11:43:35.243 security: debug 3: client 64.186.57.164#15508: request is not signed
23-May-2005 11:43:35.243 security: debug 3: client 64.186.57.164#15508: recursion available
23-May-2005 11:43:35.243 security: debug 3: client 64.186.57.164#15508: query (cache) 'lsj.com/AAAA/IN' approved
23-May-2005 11:43:35.243 general: debug 3: clientmgr @0x81ccf98: createclients
23-May-2005 11:43:35.243 general: debug 3: clientmgr @0x81ccf98: create new
23-May-2005 11:43:35.243 resolver: debug 1: createfetch: lsj.com AAAA
23-May-2005 11:43:35.243 resolver: debug 3: fctx 0x81aed88(lsj.com/AAAA'): create
23-May-2005 11:43:35.244 resolver: debug 3: fctx 0x81aed88(lsj.com/AAAA'): join
23-May-2005 11:43:35.244 resolver: debug 3: fetch 0x8190fc0 (fctx 0x81aed88(lsj.com/AAAA)): created
23-May-2005 11:43:35.244 security: debug 3: client 159.54.39.100#54640: request is not signed
23-May-2005 11:43:35.244 security: debug 3: client 159.54.39.100#54640: recursion available
23-May-2005 11:43:35.244 security: debug 3: client 159.54.39.100#54640: query (cache) 'bellsouth.net/MX/IN' approved
23-May-2005 11:43:35.244 general: debug 3: clientmgr @0x81ccf98: createclients
23-May-2005 11:43:35.244 general: debug 3: clientmgr @0x81ccf98: create new
23-May-2005 11:43:35.244 resolver: debug 1: createfetch: bellsouth.net MX
23-May-2005 11:43:35.244 resolver: debug 3: fctx 0x81b2b28(bellsouth.net/MX'): create
23-May-2005 11:43:35.244 resolver: debug 3: fctx 0x81b2b28(bellsouth.net/MX'): join
23-May-2005 11:43:35.244 resolver: debug 3: fetch 0x81b4ae0 (fctx 0x81b2b28(bellsouth.net/MX)): created
23-May-2005 11:43:35.244 resolver: debug 3: fctx 0x81aed88(lsj.com/AAAA'): start
23-May-2005 11:43:35.244 resolver: debug 3: fctx 0x81aed88(lsj.com/AAAA'): try
23-May-2005 11:43:35.244 resolver: debug 3: fctx 0x81aed88(lsj.com/AAAA'): cancelqueries
23-May-2005 11:43:35.244 resolver: debug 3: fctx 0x81aed88(lsj.com/AAAA'): getaddresses
23-May-2005 11:43:35.244 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.244 resolver: debug 3: res 0x81d6e70: priming
23-May-2005 11:43:35.244 resolver: debug 1: createfetch: . NS
23-May-2005 11:43:35.244 resolver: debug 3: fctx 0x81fb300(./NS'): create
23-May-2005 11:43:35.244 resolver: debug 3: fctx 0x81fb300(./NS'): join
23-May-2005 11:43:35.244 resolver: debug 3: fetch 0x81b3ed8 (fctx 0x81fb300(./NS)): created
23-May-2005 11:43:35.244 database: debug 5: dns_adb_createfind: found A for name 0x81fb248 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81fb190 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81fb0d8 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81fb020 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81faf68 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81faeb0 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81fadf8 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81fad40 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81fac88 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81fabd0 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81fab18 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81faa60 in db
23-May-2005 11:43:35.259 resolver: debug 3: res 0x81d6e70: dns_resolver_prime
23-May-2005 11:43:35.259 database: debug 5: dns_adb_createfind: found A for name 0x81fa9a8 in db
23-May-2005 11:43:35.259 resolver: debug 3: fctx 0x81aed88(lsj.com/AAAA'): query
23-May-2005 11:43:35.259 resolver: debug 3: resquery 0x81fcc38 (fctx 0x81aed88(lsj.com/AAAA)): send
23-May-2005 11:43:35.260 resolver: debug 3: resquery 0x81fcc38 (fctx 0x81aed88(lsj.com/AAAA)): sent
23-May-2005 11:43:35.260 resolver: debug 3: resquery 0x81fcc38 (fctx 0x81aed88(lsj.com/AAAA)): senddone
23-May-2005 11:43:35.260 security: debug 3: client 204.155.170.175#59317: request is not signed
23-May-2005 11:43:35.260 security: debug 3: client 204.155.170.175#59317: recursion available
23-May-2005 11:43:35.260 security: debug 3: client 204.155.170.175#59317: query (cache) '181.44.94.131.in-addr.arpa/PTR/IN' approved
23-May-2005 11:43:35.260 general: debug 3: clientmgr @0x81ccf98: createclients
23-May-2005 11:43:35.260 general: debug 3: clientmgr @0x81ccf98: create new
23-May-2005 11:43:35.260 resolver: debug 1: createfetch: 181.44.94.131.in-addr.arpa PTR
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x82003c8(181.44.94.131.in-addr.arpa/PTR'): create
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x82003c8(181.44.94.131.in-addr.arpa/PTR'): join
23-May-2005 11:43:35.260 resolver: debug 3: fetch 0x82003b8 (fctx 0x82003c8(181.44.94.131.in-addr.arpa/PTR)): created
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81b2b28(bellsouth.net/MX'): start
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81b2b28(bellsouth.net/MX'): try
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81b2b28(bellsouth.net/MX'): cancelqueries
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81b2b28(bellsouth.net/MX'): getaddresses
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81b2b28(bellsouth.net/MX'): query
23-May-2005 11:43:35.260 resolver: debug 3: resquery 0x8202218 (fctx 0x81b2b28(bellsouth.net/MX)): send
23-May-2005 11:43:35.260 resolver: debug 3: resquery 0x8202218 (fctx 0x81b2b28(bellsouth.net/MX)): sent
23-May-2005 11:43:35.260 resolver: debug 3: resquery 0x8202218 (fctx 0x81b2b28(bellsouth.net/MX)): senddone
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81fb300(./NS'): start
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81fb300(./NS'): try
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81fb300(./NS'): cancelqueries
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81fb300(./NS'): getaddresses
23-May-2005 11:43:35.260 resolver: debug 3: fctx 0x81fb300(./NS'): query
23-May-2005 11:43:35.260 resolver: debug 3: resquery 0x8203408 (fctx 0x81fb300(./NS)): send
23-May-2005 11:43:35.260 resolver: debug 3: resquery 0x8203408 (fctx 0x81fb300(./NS)): sent
23-May-2005 11:43:35.260 resolver: debug 3: resquery 0x8203408 (fctx 0x81fb300(./NS)): senddone
23-May-2005 11:43:35.261 security: debug 3: client 63.175.130.5#2381: request is not signed
23-May-2005 11:43:35.261 security: debug 3: client 63.175.130.5#2381: recursion available
23-May-2005 11:43:35.261 security: debug 3: client 63.175.130.5#2381: query (cache) '2.163.22.208.malaysia.blackholes.us/TXT/IN' approved
23-May-2005 11:43:35.261 general: debug 3: clientmgr @0x81ccf98: createclients
23-May-2005 11:43:35.261 general: debug 3: clientmgr @0x81ccf98: create new
23-May-2005 11:43:35.261 resolver: debug 1: createfetch: 2.163.22.208.malaysia.blackholes.us TXT
23-May-2005 11:43:35.261 resolver: debug 3: fctx 0x8205af0(2.163.22.208.malaysia.blackholes.us/TXT'): create
23-May-2005 11:43:35.261 resolver: debug 3: fctx 0x8205af0(2.163.22.208.malaysia.blackholes.us/TXT'): join
23-May-2005 11:43:35.261 resolver: debug 3: fetch 0x8205ae0 (fctx 0x8205af0(2.163.22.208.malaysia.blackholes.us/TXT)): created
23-May-2005 11:43:35.261 resolver: debug 3: fctx 0x82003c8(181.44.94.131.in-addr.arpa/PTR'): start
23-May-2005 11:43:35.261 resolver: debug 3: fctx 0x82003c8(181.44.94.131.in-addr.arpa/PTR'): try
23-May-2005 11:43:35.261 resolver: debug 3: fctx 0x82003c8(181.44.94.131.in-addr.arpa/PTR'): cancelqueries
23-May-2005 11:43:35.261 resolver: debug 3: fctx 0x82003c8(181.44.94.131.in-addr.arpa/PTR'): getaddresses
23-May-2005 11:43:35.261 resolver: debug 3: fctx 0x82003c8(181.44.94.131.in-addr.arpa/PTR'): query
23-May-2005 11:43:35.261 resolver: debug 3: resquery 0x8207410 (fctx 0x82003c8(181.44.94.131.in-addr.arpa/PTR)): send

On Sun, May 22, at 10:38%P so wrote Barry Margolin (barmar at alum.mit.edu):

> In article <d6q1v8$2as$1 at sf1.isc.org>, Maria Iano <maria at iano.org> 
> wrote:
> 
> > I ran netstat -a and saw that nothing was listening to port 53 at the 
> > time. Then I restarted Bind and saw that tcp 53 was being listened to, 
> > and tcp DNS queries were answered. Then I restarted Bind and netstat -a 
> > showed tcp port 53 was not being listened to, and tcp DNS queries were 
> > not answered, and then I restarted Bind and tcp port 53 was being 
> > listened to and tcp DNS queries were answered, and so on...  It 
> > appeared to be alternating, but I only restarted it about 7 times so 
> > that could easily just be coincidence.
> 
> I'll ask again -- is named logging any errors during the cases when it 
> fails?
> 
> -- 
> Barry Margolin, barmar at alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
> 



More information about the bind-users mailing list