pdnsd resolvconf script causes pdnsd to go into endless loop
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
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
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 |
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.