[Pdns-dev] powerDNS resolving one domain but not another hosted on the same instance

[bert hubert]

On Tue, Apr 17, 2007 at 01:02:54PM -0400, Donald Knights wrote:

> The first site (www.designknights.com) on 66.93.230.35 works fine.
> The second site (www.edensidechristian.org) on 66.93.230.136 does not. 

Donald,

These are the nameservers for edensidechristian.org:
;; ADDITIONAL SECTION:
ns1.edensidechristian.org. 86286 IN     A       66.93.230.128
ns2.edensidechristian.org. 86286 IN     A       66.93.230.35

These are the nameservers for designknights.com:
ns2.designknights.com.  172763  IN      A       66.93.230.135
ns1.designknights.com.  172763  IN      A       66.93.230.128

Note how they share .128, but not .35. So we have 3 IP addresses:
66.93.230.35, 66.93.230.128 and 66.93.230.135.

Of these, only .135 answers to UDP questions on port 53. The all work over
*TCP* port 53 however. 

If we take a closer look, we see this:

82.93.240.211.37063 > 66.93.230.35.53:  9042+ A? www.designknights.com. (39)
66.93.230.135.53 > 82.93.240.211.37063:  9042*- 1/0/0 A[|domain]

Which tells us questions to 66.93.230.35 are being answered by
66.93.230.135.

This in turn means you ignored our friendly advise during startup :-)

Apr 17 19:17:04 It is advised to bind to explicit addresses with the --local-address option
Apr 17 19:17:04 UDP server bound to 0.0.0.0:5300
Apr 17 19:17:04 TCP server bound to 0.0.0.0:5300

Please add the following to your configuration:

local-address=66.93.230.35,66.93.230.128,66.93.230.135

And things will work as intended. Right now PowerDNS is unable to properly
answer queries from the right IP address. BIND gets this right
automatically, at the expense of around a thousand lines of code, something
we've not yet found the time or energy for.

Good luck!

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services