[Pdns-users] Problems with supermaster
bas at bserved.nl
Sat Jul 3 19:35:21 UTC 2004
Ok, forget my ignorance, setting the 'query-local-address' in both configs
solved the whole situation ;)
----- 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
> I'm sorry if this was already answered somewhere, but I couldn't find it.
> 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 188.8.131.52
> ns2.domain.nl - Listens on 184.108.40.206
> In ns1.domain.nl I have a zone 'blaat.nl'. I
> In the database for ns2.domain.nl I have added a supermaster record:
> 220.127.116.11 / ns2.domain.nl.
> When PowerDNS tries to update te zone, the following shows up in the ns1
> Jul 03 20:43:15 UDP server bound to 18.104.22.168:53
> Jul 03 20:43:15 TCP server bound to 22.214.171.124:53
> Jul 03 20:43:15 PowerDNS 2.9.16 (C) 2001-2004 PowerDNS.COM BV (May 14
> 14:08:25) starting up
> Jul 03 20:43:56 Queued notification of domain 'blaat.nl' to 126.96.36.199
> Jul 03 20:43:56 Queued notification of domain 'blaat.nl' to 188.8.131.52
> Jul 03 20:43:56 Received NOTIFY for blaat.nl from 184.108.40.206 but slave
> support is disabled in the configuration
> Jul 03 20:43:57 Received unsuccesful notification report for 'blaat.nl'
> 220.127.116.11, rcode: 4
> Jul 03 20:43:57 Removed from notification list: 'blaat.nl' to
> Jul 03 20:43:58 Received unsuccesful notification report for 'blaat.nl'
> 18.104.22.168, rcode: 2
> Jul 03 20:43:58 Removed from notification list: 'blaat.nl' to
> Jul 03 20:43:59 No master domains need notifications
> and in ns2:
> Jul 03 20:43:47 Received NOTIFY for blaat.nl from 22.214.171.124 for which
> we are not authoritative
> Jul 03 20:43:48 Error resolving SOA or NS for 'blaat.nl' at 126.96.36.199
> So it seems powerdns on ns1 just picks a random IP (the last one added in
> case) and connects to ns2, which expects the .127 ip and says it isn't
> 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
More information about the Pdns-users