[bitfolk] Re: question on bind9 listening.

Hi, On the logs it failed to listen x.x.x.x address at port 53. Once I put the listen directive to any IP address bind started to work again. Anyhow for the powerdns it is both a primary and secondary operations. I put all the IP's for for secondary to the allow-axfr-ips. Yes after doing dig -t axfr testingsforonedomains.com @x.x.x.x the axfr is working on the secondary. Could be a miss configurations I suppose. Thanks. Regards, -badli ________________________________ From: Andy Smith via BitFolk Users <users(a)mailman.bitfolk.com> Sent: Sunday, April 23, 2023, 03:33 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 06:46:10PM +0000, Badli Al Rashid via BitFolk Users wrote: I think it's fine. Most of the time you're running a DNS server because you want it to be globally reachable anyway. If it's a resolver then it might make more sense to only have it listen on certain interfaces. Logs will say why. Logs are really good. They save a lot of time from posting messages about how "it failed" as they usually tell you why "it failed". These just sound like misconfigurations. - Decide what you want to do. - Tackle one problem at a time. - Show exact configuration, logs and/or copy of output showing what it did, and explanation of what you actually wanted it to do. You can test if an AXFR works, requesting from your BIND host to your PowerDNS host, without even using BIND. You can test it with just "dig": $ dig -b 192.168.1.2 -t axfr example.com @10.10.1.2 Where: - 192.168.1.2 is the source address you want the AXFR to come from - example.com is the zone you want to transfer from PowerDNS - 10.10.1.2 is the IP address of POwerDNS Get that working first. Once it works, configure BIND to do the same. Cheers, Andy