Ubuntu
pdns-recursor package

Can't decide priority for 127.0.0.1 on /etc/resolv.conf

Bug #1130651 reported by Daniele Valeriani
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pdns-recursor (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

The start_resolvconf() and stop_resolvconf() functions in /etc/init.d/pdns-recursor can only append 127.0.0.1 to the list of nameservers in /etc/resolv.conf.

There should be a way to add it on the top of the list to prioritise the use of the local cache instead of the external dns resolvers first.
It could be a new config parameter in /etc/powerdns/recursor.conf but it's really up to you guys.

Thanks!

See original description
Daniele Valeriani (omame)
description: updated
Revision history for this message
Chris Hofstaedtler (zeha) wrote :

Reassigning to resolvconf as that's a general thing, not pdns-recursor specific.

affects: pdns-recursor (Ubuntu) → resolvconf (Ubuntu)
Revision history for this message
Thomas Hood (jdthood) wrote :

To prioritize pdns-recursor's listen address in resolv.conf, edit /etc/resolvconf/interface-order and replace the line

     lo.!(pdns|pdns-recursor)

with the following line.

    lo.*

See https://bugs.debian.org/308677 for background.

affects: resolvconf (Ubuntu) → pdns-recursor (Ubuntu)
Changed in pdns-recursor (Ubuntu):
status: New → Incomplete
Mathew Hodson (mhodson)
Changed in pdns-recursor (Ubuntu):
status: Incomplete → Invalid
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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