[Pdns-users] Problem with Multihomed pdns server...

Matthew Walker mwalker at kydance.net
Thu Apr 24 16:29:10 UTC 2003


I've got a machine running pdns that has several aliased IP addresses on one
NIC. Two of them are used as nameserver IPs, and when I was running BIND,
that setup worked perfectly. Now, however, pdns listens on both IPs, but
only answers on one of them... This is causing problems. I've included some
'dig' output below to illustrate the problem.

mommybox root # dig @216.190.203.133 forgeglobal.com
;; reply from unexpected source: 216.190.203.134#53, expected
216.190.203.133#53
;; reply from unexpected source: 216.190.203.134#53, expected
216.190.203.133#53

However, when I dig with the other IP for the box, this is what I get:

mommybox root # dig @216.190.203.134 forgeglobal.com

; <<>> DiG 9.2.2rc1 <<>> @216.190.203.134 forgeglobal.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26542
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;forgeglobal.com.               IN      A

;; ANSWER SECTION:
forgeglobal.com.        259200  IN      A       216.190.203.152

;; Query time: 111 msec
;; SERVER: 216.190.203.134#53(216.190.203.134)
;; WHEN: Thu Apr 24 11:23:55 2003
;; MSG SIZE  rcvd: 49


This is causing some problems with resolving domains, obviously, since some
clients apparently just sit and loop on the first IP address, and don't
listen to the response from the wrong address. Is there any way I can fix
this?

Matthew Walker




More information about the Pdns-users mailing list