Maintained by: NLnet Labs

forward-zone: .

M. Piscaer
Thu Nov 24 11:06:23 CET 2016



On 24-11-16 09:08, W.C.A. Wijngaards via Unbound-users wrote:
> Hi Michiel,
> 
> On 23/11/16 21:34, M. Piscaer via Unbound-users wrote:
>> Hi,
>>
>> I try to forward all query's to an central dns resolver.
>>
>> In the config of the unbound service I have the following setting:
>>
>> forward-zone:
>>   name: "com."
>>   forward-addr: 192.168.1.1
>>   forward-addr: 192.168.1.2
>>
>> forward-zone:
>>   name: "."
>>   forward-addr: 192.168.1.1
>>   forward-addr: 192.168.1.2
>>
>> After reloading the unbound service, I only see the .com in de
>> forwarding table:
>>
>> #unbound-control list_forwards
>> com. IN forward: 192.168.1.1 192.168.1.2
> 
> For me, the config works fine, and lists
> . IN forward 192.168.1.1 192.168.1.2
> com. IN forward 192.168.1.1 192.168.1.2
> 
> For you this does not work?  Are you changing the correct config file
> (on some systems you can pick the wrong one)?  If you start unbound with
> (high) verbosity, it'll print the forward zones that are configured at
> startup to the (sys-)log.
> 
> Best regards, Wouter
> 
>>
>>
>> When I remove the .com zone the unbound service doesn't use the central
>> server?
>>
>> Kind regards,
>>
>> Michiel Piscaer
>>
> 
> 

I found the solution, in the file /etc/default/unbound the variable
RESOLVCONF and RESOLVCONF_FORWARDERS are set to true.

In the /etc/resolve.conf I had:

nameserver 127.0.0.1
nameserver 88.159.1.200
nameserver 88.159.1.201

Probably of the localhost the system ignors or got an error and did add
the lines and also ignores the forward in the config.


Kind regards,

Michiel Piscaer

-- 
Network / System Engineer
Security Officer

E-mail:   m.piscaer at edutel.nl
Telefoon: +31 88 787 0209
Fax:      +31 88 787 0502
Mobiel:   +31 6 16048782
Threema:  PBPCM9X3
PGP:      0x592097DB
W3:       www.edutel.nl