[bitfolk] Re: question on bind9 listening.

Hi Andy, Below are the logs for opening up the firewall but I can not find the logs that says fail to listen on address. When I open Port 53 was to all not just 2 IP address my axfr was completed. Hope I be able to explain it properly. foronedomain.com/IN: sending notifies (serial 20230 41906) 19-Apr-2023 08:36:55.075 general: info: received co ntrol channel command 'stop' 19-Apr-2023 08:36:55.075 network: info: no longer l istening on 127.0.0.1#53 19-Apr-2023 08:36:55.075 network: info: no longer l istening on 85.119.83.49#53 19-Apr-2023 08:36:55.079 network: info: no longer l istening on 85.119.82.135#53 19-Apr-2023 08:36:55.079 network: info: no longer l istening on ::1#53 19-Apr-2023 08:36:55.079 network: info: no longer l istening on 2001:ba8:1f1:f0b5::2#53 19-Apr-2023 08:36:55.079 network: info: no longer l istening on fe80::216:5eff:fe00:5f5%2#53 Full part. 19-Apr-2023 08:01:45.149 xfer-in: info: 0x7f5d90e31 c00: transfer of 'testingforonedomain.com/IN' from 2400:8901::f03c:93ff:fe63:5988#53: Transfer complet ed: 3 messages, 14 records, 512 bytes, 0.624 secs ( 820 bytes/sec) (serial 2023041906) 19-Apr-2023 08:01:45.149 notify: info: zone testing foronedomain.com/IN: sending notifies (serial 20230 41906) 19-Apr-2023 08:36:55.075 general: info: received co ntrol channel command 'stop' 19-Apr-2023 08:36:55.075 network: info: no longer l istening on 127.0.0.1#53 19-Apr-2023 08:36:55.075 network: info: no longer l istening on 85.119.83.49#53 19-Apr-2023 08:36:55.079 network: info: no longer l istening on 85.119.82.135#53 19-Apr-2023 08:36:55.079 network: info: no longer l istening on ::1#53 19-Apr-2023 08:36:55.079 network: info: no longer l istening on 2001:ba8:1f1:f0b5::2#53 19-Apr-2023 08:36:55.079 network: info: no longer l istening on fe80::216:5eff:fe00:5f5%2#53 19-Apr-2023 08:36:55.079 general: notice: stopping command channel on 127.0.0.1#953 19-Apr-2023 08:36:55.079 general: notice: stopping command channel on ::1#953 19-Apr-2023 08:36:55.079 general: info: shutting do wn: flushing changes 19-Apr-2023 08:36:55.119 general: info: configuring command channel from '/etc/bind/rndc.key' 19-Apr-2023 08:36:55.119 general: notice: command c hannel listening on 127.0.0.1#953 19-Apr-2023 08:36:55.119 general: info: configuring command channel from '/etc/bind/rndc.key' 19-Apr-2023 08:36:55.119 general: notice: command c hannel listening on ::1#953 19-Apr-2023 08:36:55.119 zoneload: info: managed-ke ys-zone: loaded serial 103 19-Apr-2023 08:36:55.119 zoneload: info: zone 0.in- addr.arpa/IN: loaded serial 1 19-Apr-2023 08:36:55.119 zoneload: info: zone 127.i n-addr.arpa/IN: loaded serial 1 19-Apr-2023 08:36:55.119 zoneload: info: zone 255.i n-addr.arpa/IN: loaded serial 1 19-Apr-2023 08:36:55.119 zoneload: info: zone testi ngforonedomain.com/IN: loaded serial 2023041906 19-Apr-2023 08:36:55.119 zoneload: info: zone local host/IN: loaded serial 2 19-Apr-2023 08:36:55.119 zoneload: info: zone zystr o.xyz/IN: loaded serial 2023041901 19-Apr-2023 08:36:55.119 general: notice: all zones loaded 19-Apr-2023 08:36:55.119 general: notice: running 19-Apr-2023 08:36:55.119 notify: info: zone zystro. xyz/IN: sending notifies (serial 2023041901) 19-Apr-2023 08:36:55.119 notify: info: zone testing foronedomain.com/IN: sending notifies (serial 20230 41906) 19-Apr-2023 08:36:55.123 dnssec: info: managed-keys -zone: Key 20326 for zone . is now trusted (accepta nce timer complete) 19-Apr-2023 08:36:55.127 resolver: info: resolver p riming query complete: success 19-Apr-2023 08:36:55.535 xfer-out: info: client @0x 7f4fb4895c00 2605:2700:0:2:a800:ff:fe69:e7a7#34291 (zystro.xyz): transfer of 'zystro.xyz/IN': IXFR ver sion not in journal, falling back to AXFR 19-Apr-2023 08:36:55.535 xfer-out: info: client @ Regards, -badli ________________________________ From: Andy Smith via BitFolk Users <users(a)mailman.bitfolk.com> Sent: Sunday, April 23, 2023 5:54:36 AM To: users(a)mailman.bitfolk.com <users(a)mailman.bitfolk.com> Cc: Andy Smith <andy(a)bitfolk.com> Subject: [bitfolk] Re: question on bind9 listening. Hi Badli, On Sat, Apr 22, 2023 at 09:29:58PM +0000, Badli Al Rashid via BitFolk Users wrote: You aren't going to get any useful help unless you show the actual relevant log lines, in full (I guarantee this isn't it) without obscuring any IP addresses. The obvious conclusion from that is that you tried to make it listen on an interface:port that it could not listen on, for reasons that it almost certainly has told you in the logs. By not asking it to do that… it doesn't do that. Fine if you didn't actually want to do that. If you did want to make it listen on only specified interfaces, then you have a problem. Let's solve that problem then. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting