pdnsd resolvconf script causes pdnsd to go into endless loop

Bug #70735 reported by Hadmut Danisch
6
Affects Status Importance Assigned to Milestone
pdnsd (Debian)
Fix Released
Unknown
pdnsd (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: pdnsd

Hi,

when using pdnsd with resolvconf, the pdnsd's script
/etc/resolvconf/update.d/pdnsd causes an endless loop if the machine
does not have internet connection. At boottime /etc/init.d/pdnsd sets 127.0.0.1 as a default nameserver for the lo device to override all other settings
for other interfaces, as it is expected to be. That's ok.

But then, the resolvconf passes this through to
/etc/resolvconf/update.d/pdnsd which sets the pdnsd's parent
nameserver "resolvconf" to 127.0.0.1, causing pdnsd to go into an
endless loop querying itself when been asked for any address.

The script needs to eliminate 127.0.0.1 from the list of servers to be
set and never let pdnsd query itself.

regards
Hadmut

Changed in pdnsd:
status: Unknown → Unconfirmed
Changed in pdnsd:
status: New → Fix Released
Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Hi,

Thanks for your bug report. This issue is fixed in debian with the 1.2.5par-1 package, which unfortunately didn't make it into gutsy. I'll be auto-synced for gutsy+1 though.

Changed in pdnsd:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

Fixed in hardy

Changed in pdnsd:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.