Project

General

Profile

Bug #7152

Unbound / DNS Resolver issue if "Register DHCP static mappings in the DNS Resolver" set before wildcard DNS custom options

Added by Rudolph Sand almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
01/22/2017
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.3.2
Affected Architecture:

Description

Tested on:
2.3.2-RELEASE-p1 (amd64)
built on Tue Sep 27 12:13:07 CDT 2016
FreeBSD 10.3-RELEASE-p9

To create the bug:
1) Enable DNS Resolver, and enable "Register DHCP static mappings in the DNS Resolver".
Save, apply.
2) Wait (like 2 seconds) for one client with a static DHCP mapping to register itself in the DNS...

3) Now try to add a wildcard DNS alias in "Custom Options", as specified in https://doc.pfsense.org/index.php/Wildcard_Records_in_DNS_Forwarder/Resolver
server:
local-zone: "example.com" redirect
local-data: "example.com 86400 IN A 192.168.1.54" 

Result:
Cannot save the unbound config file because the wildcard alias isn't on top of unbound.conf ...

Way to get around the bug:
1) Disable "Register DHCP static mappings in the DNS Resolver", save, apply
2) Add the wildcard DNS alias as instructed in the above url, save, apply
3) Enable "Register DHCP static mappings in the DNS Resolver", save, apply

Why is this a bug ?:
Because each time you need to add/modify a wildcard setting (which happens to me more often than you think), you need to do all the "way to get around the bug", which feels kind of .. silly.

Thank you all for making pfSense what it is.

Best regards

rud.

Also available in: Atom PDF