Hurricane Electric's IPv6 Tunnel Broker Forums

DNS.HE.NET Topics => General Questions & Suggestions => Topic started by: lgwapnitsky on February 20, 2022, 08:06:28 AM

Title: Unsuccessful notification reports
Post by: lgwapnitsky on February 20, 2022, 08:06:28 AM
I've configured PowerDNS to send "notify" requests to ns1.he.net. I'm receiving the following in my logs consistently:

Feb 20 10:44:28 ns1 pdns_server[55090]: Received unsuccessful notification report for 'test.domain.com' from 216.218.130.2:53, error: Query Refused
Feb 20 10:44:31 ns1 pdns_server[55090]: Received unsuccessful notification report for 'test.domain.com' from [2001:470:100::2]:53, error: Query Refused

(edited name of real domain)

Any suggestions?

Thank you
Title: Re: Unsuccessful notification reports
Post by: passport123 on February 20, 2022, 08:23:07 AM
> Any suggestions?


Maybe show a tcpdump of the outgoing and incoming notification packets.  That would help narrow down a problem.

 
Title: Re: Unsuccessful notification reports
Post by: divad27182 on May 11, 2022, 06:06:54 PM
I believe you must notify slave.dns.he.net
Title: Re: Unsuccessful notification reports
Post by: ewb on May 12, 2022, 01:48:10 PM
Correct.  The "also-notify" line for BIND will look something like this in context:

        zone "example.com" {
                type master;
                file "db.example.com";
                also-notify { 216.218.130.2; };
                allow-update { none; };
        };