Project

General

Profile

Actions
Copy link

Bug #4095

closed

Unbound config not regenrated on WAN-style interface acquiring IP address

Added by Phillip Davis over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Chris Buechler
Category:
DNS Resolver
Target version:
2.2
Start date:
12/10/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:

Description

Example: system with dual-WAN - WAN and OPT1 both DHCP.
Boot with WAN getting DHCP but OPT1 connected but not getting DHCP.
Unbound in forwarding mode, no DNS servers explicitly in General Setup, "Allow DNS server list to be overridden by DHCP/PPP on WAN" checked.

unbound.conf has forwarders section like:
--------
  1. Forwarding
    forward-zone:
    name: "."
    forward-addr: 10.172.1.1
    --------
    10.721.1.1 is the WAN DHCP-given gateway - good.

Now fix the problem upstream of OPT1 so it gets an IP address by DHCP.
apinger, gateway groups and associated rules do their thing - good.
But unbound.conf is not re-generated - it still has a single forward-addr listed.
Now WAN goes down (with some upstream problem - apinger detects 100% packet loss). Again nothing regenerates unbound.conf.
Now routing is all working fine. If you know the IP addresses of everything on the internet you are fine! But DNS is not working because unbound only knows about 10.172.1.1, which does not work any more.

Something needs to give unbound.conf a re-generate when WAN-style links have an IP address change, and particularly when Unbound is in forwarding mode and using the DNS servers learned from DHCP.
(If the DNS servers are all specified in General Setup, then there should be no problem - the fully-populated unbound.conf would be generated at boot time, whether every WAN link is up or not)

Actions
Copy link

Also available in: Atom PDF