Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stub resolver should reload /etc/resolv.conf #6263

Closed
mnordhoff opened this issue Feb 13, 2018 · 0 comments
Closed

Stub resolver should reload /etc/resolv.conf #6263

mnordhoff opened this issue Feb 13, 2018 · 0 comments

Comments

@mnordhoff
Copy link
Contributor

  • Program: Authoritative
  • Issue type: Bug report

Short description

When "resolver" isn't set, auth's stub resolver reads /etc/resolv.conf once at startup to determine what nameservers to use.

It uses them forever, even if /etc/resolv.conf is later changed.

Environment

  • Operating system: Ubuntu 16.04 (x86-64)
  • Software version: 4.1.0-1pdns.xenial
  • Software source: PowerDNS repository

Steps to reproduce

  1. Start PowerDNS.
  2. Change /etc/resolv.conf to use different nameservers.
  3. Wait for PowerDNS to do a secpoll query.

Expected behaviour

PowerDNS querying one of the nameservers currently in /etc/resolv.conf.

Actual behaviour

PowerDNS querying the nameserver that was in /etc/resolv.conf when it started.

Other information

I use resolvconf. Last time I rebooted, it changed /run/resolvconf/resolv.conf from a nameserver I don't like to a nameserver I do like 1 second after PowerDNS was started. Sad face.

It's not a problem for me, it just makes me unhappy.

I don't often change /etc/resolv.conf.

@pieterlexis pieterlexis added this to the auth-helpneeded milestone Feb 14, 2018
pieterlexis added a commit that referenced this issue Mar 21, 2018
Auth: Reload /etc/resolv.conf when modified. Fix #6263
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants