Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Unsuccessful notification reports  (Read 665 times)

lgwapnitsky

  • Newbie
  • *
  • Posts: 3
Unsuccessful notification reports
« 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
Logged

passport123

  • Newbie
  • *
  • Posts: 47
Re: Unsuccessful notification reports
« Reply #1 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.

 
Logged

divad27182

  • Jr. Member
  • **
  • Posts: 70
Re: Unsuccessful notification reports
« Reply #2 on: May 11, 2022, 06:06:54 PM »

I believe you must notify slave.dns.he.net
Logged

ewb

  • Newbie
  • *
  • Posts: 1
Re: Unsuccessful notification reports
« Reply #3 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; };
        };
Logged