Re: [Pdns-users] PowerDNS suddenly refuses to resolve
I'm not entirely sure how, but the conversation that followed this went off-list. For completeness, though, I can declare this matter closed. After some sterling help from Brian Candler, to whom I owe my grateful thanks, this turned out to be a typo in the DNS file, and nothing to do with PowerDNS at all. Thanks for the help! Cheers, Laurie. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PowerDNS suddenly refuses to resolve
On 24/06/2021 12:03, Laurie Brown via Pdns-users wrote: One of my pdns name servers has suddenly stopped resolving, giving a status to dig of status: REFUSED. I have no idea why as it was working perfectly well for several days (it's a new installation). Quite possibly because it's not running powerdns at all, it's running bind 9 - or at least claims to be. $ dig +short @ns6.convergent-ict.com version.bind txt chaos "9.16.1-Ubuntu" $ dig +short @ns7.convergent-ict.com version.bind txt chaos "PowerDNS Authoritative Server 4.2.1" Maybe what has happened is that someone has installed/started bind on that server, it bound to port 53, and this in turn is stopping powerdns from starting. BTW, this makes it very clear why the "out in the open" support policy is so important! :-) Also, do note that powerdns 4.2 is due to go end-of-life soon: https://doc.powerdns.com/authoritative/appendices/EOL.html Regards, Brian. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] PowerDNS suddenly refuses to resolve
Hi all, One of my pdns name servers has suddenly stopped resolving, giving a status to dig of status: REFUSED. I have no idea why as it was working perfectly well for several days (it's a new installation). My other nameserver, which is a renamed clone of this one, continues to work perfectly well. Thankfully! I'm using PowerDNS 4.2.1-1build2, on Ubuntu Server 20.04, on a Digital Ocean VPS. Firewalling is not an issue as port 53 is open. I have the tinydns backend enabled as I migrated from DJBdns, and haven't had time to get an sql file sorted out for import. Here's the dig result in full: dig convergent-ict.com NS @ns6.convergent-ict.com ; <<>> DiG 9.16.1-Ubuntu <<>> convergent-ict.com NS @ns6.convergent-ict.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 53199 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: d07f034bc11da98d010060d465f80d8dc0242f4c7077 (good) ;; QUESTION SECTION: ;convergent-ict.com.IN NS ;; Query time: 31 msec ;; SERVER: 165.22.194.246#53(165.22.194.246) ;; WHEN: Thu Jun 24 12:01:12 BST 2021 ;; MSG SIZE rcvd: 75 Obviously the errant server is ns6.convergent-ict.com, and for completeness, the one that's working is ns7.convergent-ict.com Thanks in advance for any help. Cheers, Laurie. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
