pfSense

Adding the following to the DNS Resolver Custom options field:

private-domain: example.org

...results in the following error:

The following input errors were detected:

• The generated config file cannot be parsed by unbound. Please correct the following errors:
• /var/unbound/test/unbound.conf:116: error: syntax error
• read /var/unbound/test/unbound.conf failed: 1 errors in configuration file

The offending config snippet:

...

# Access lists
include: /var/unbound/test/access_lists.conf

# Static host entries
include: /var/unbound/test/host_entries.conf

# dhcp lease entries
include: /var/unbound/test/dhcpleases_entries.conf

# Domain overrides
include: /var/unbound/test/domainoverrides.conf
# Forwarding
forward-zone:
        name: "." 
        forward-tls-upstream: yes
        forward-addr: 9.9.9.9@853
        forward-addr: 1.1.1.1@853

# Unbound custom options
private-domain: example.org

...

It's possible that this is a bug in Unbound. I can confirm the issue manually:

[2.4.4-RELEASE][admin@pfsense.example.org]/root: unbound-checkconf /var/unbound/test/unbound.conf
/var/unbound/test/unbound.conf:116: error: syntax error
read /var/unbound/test/unbound.conf failed: 1 errors in configuration file

If I manually move the private-domain directive above the first include directive, the config passes happily:

[2.4.4-RELEASE][admin@pfsense.example.org]/root: unbound-checkconf /var/unbound/test/unbound.conf
unbound-checkconf: no errors in /var/unbound/test/unbound.conf