Project

General

Profile

Actions

Bug #4090

closed

unbound advanced settings cause broken unbound.conf file

Added by Vick Khera over 9 years ago. Updated about 9 years ago.

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

100%

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

Description

I need to permit private IPs for my local domains to resolve. That is, vick.int.kcilink.com resolves to 192.168.7.80. To this end, I have to tell unbound that kcilink.com (and my other domains) is allowed to have private addresses with this configuration:

private-domain: "kcilink.com" 
private-domain: "m1e.net" 
private-domain: "mailermailer.com" 
private-domain: "khera.org" 

The above is exactly what is in the "Advanced" box of the unbound general configuration.

In the unbound.conf file it is emitted as one line with no newlines:

private-domain: "kcilink.com"private-domain: "m1e.net"private-domain: "mailermailer.com"private-domain: "khera.org" 

which causes unbound do fail to restart.

Ideally, there would be a UI for adding such domains, as I'm sure many people need this feature for their office hosts.


Files

unbound.conf (1.19 KB) unbound.conf unbound config file section Vick Khera, 12/18/2014 06:46 AM
config-pfsense.localdomain-20150105090641.xml (20.5 KB) config-pfsense.localdomain-20150105090641.xml Vick Khera, 01/05/2015 08:06 AM
Actions

Also available in: Atom PDF