Project

General

Profile

Actions
Copy link

Bug #11263

closed

Unbound fails to parse config if DNS Query Forwarding and custom options are enabled

Added by Konstantin Svist over 5 years ago. Updated over 5 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
01/18/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.5-p1
Affected Architecture:

Description

I tried to enable DNS Query Forwarding and I have a custom option.
unbound-checkconf fails pointing to the custom option

config segment:

# Forwarding
forward-zone:
        name: "." 
        forward-tls-upstream: yes
        forward-addr: 8.8.8.8@853
        forward-addr: 8.8.4.4@853

# Unbound custom options
log-servfail: yes

If I manually edit the file to move custom option before "forward-zone" section, file is validated as expected.
If I comment out custom option, everything is fine too.

Actions
Copy link
 #1

Updated by Konstantin Svist over 5 years ago

Looks like this can be "fixed" by prepending "server:" before the list of custom options.
This wasn't obvious from the UI, if that's the right fix, maybe there should be a text prompt mentioning how to use this?

Actions
Copy link
 #2

Updated by Jim Pingle over 5 years ago

  • Status changed from New to Not a Bug

It's a known and well documented case. Given the wide variety of what users may want to do with custom options, the UI can't make assumptions about its contents.

Actions
Copy link

Also available in: Atom