[Pdns-users] Problems with supermaster

f.caspers f.caspers at wtnet.de
Sat Jul 3 19:39:53 UTC 2004


Hi

and your supermaster record is wrong.
your say that the IP 81.173.118.127 is ns1.
And your have this record in in your ns2
81.173.118.127 / ns2.domain.nl.
???
edit this to ns1.domain.nl.

Fabian
----- Original Message ----- 
From: "Bas Verhoeven" <bas at bserved.nl>
To: <pdns-users at mailman.powerdns.com>
Sent: Saturday, July 03, 2004 8:53 PM
Subject: [Pdns-users] Problems with supermaster


> Hi,
>
> I'm sorry if this was already answered somewhere, but I couldn't find it.
I
> have set up PowerDNS on two machines both with multiple IP addresses, both
> the pdns server are bound to an IP address which works fine. I'm however
> getting errors when trying to use supermaster.
>
> My situation:
>
> ns1.domain.nl - Listens on
> ns2.domain.nl - Listens on 193.22.139.129
>
> In ns1.domain.nl I have a zone 'blaat.nl'. I
> In the database for ns2.domain.nl I have added a supermaster record:
> 81.173.118.127 / ns2.domain.nl.
>
> When PowerDNS tries to update te zone, the following shows up in the ns1
> log:
>
> Jul 03 20:43:15 UDP server bound to 81.173.118.127:53
> Jul 03 20:43:15 TCP server bound to 81.173.118.127:53
> Jul 03 20:43:15 PowerDNS 2.9.16 (C) 2001-2004 PowerDNS.COM BV (May 14
2004,
> 14:08:25) starting up
> ...
> Jul 03 20:43:56 Queued notification of domain 'blaat.nl' to 193.22.139.129
> Jul 03 20:43:56 Queued notification of domain 'blaat.nl' to 81.173.118.127
> Jul 03 20:43:56 Received NOTIFY for blaat.nl from 81.173.118.127 but slave
> support is disabled in the configuration
> Jul 03 20:43:57 Received unsuccesful notification report for 'blaat.nl'
from
> 81.173.118.127, rcode: 4
> Jul 03 20:43:57 Removed from notification list: 'blaat.nl' to
81.173.118.127
> Jul 03 20:43:58 Received unsuccesful notification report for 'blaat.nl'
from
> 193.22.139.129, rcode: 2
> Jul 03 20:43:58 Removed from notification list: 'blaat.nl' to
193.22.139.129
> Jul 03 20:43:59 No master domains need notifications
>
> and in ns2:
>
> Jul 03 20:43:47 Received NOTIFY for blaat.nl from 81.173.118.142 for which
> we are not authoritative
> Jul 03 20:43:48 Error resolving SOA or NS for 'blaat.nl' at 81.173.118.142
>
> So it seems powerdns on ns1 just picks a random IP (the last one added in
my
> case) and connects to ns2, which expects the .127 ip and says it isn't
> authorative.
> I can't find a way to set an IP to connect from though, adding the .142 in
> supermaster doesn't solve anything as ns2 probably tries to do some AXFR
> query on .142, but no dns server is listening on there.
>
> Also ns1 tries to send the zone to itself ?
>
> Anyone out there that can help me?
>
> Sincerely yours,
> Bas Verhoeven
>
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> http://mailman.powerdns.com/mailman/listinfo/pdns-users
>
> ########## ERWIN Scanner-Report #############
> Diese Nachricht wurde auf Viren und andere gefährliche
> Inhalte untersucht und ist virenfrei. SID=2
>



More information about the Pdns-users mailing list