Unbound local-zone or local-data doesn't work if the domain starts with number about unbound

[gthess]

I could not reproduce this. I also don't see a reason for that behavior in the code either.
Are you sure that you are editing a configuration file that is read by the running Unbound?
If so, maybe you have conflicting configuration later on in the file?

[presci]

Here is my unbound.conf
`
server:
interface: 0.0.0.0

access-control: 192.168.0.0/24 allow
access-control: 127.0.0.1 allow
access-control: ::1 allow
access-control: 0.0.0.0/0 deny
access-control: ::/0 deny


pidfile: "/var/run/unbound.pid"
use-syslog: yes
verbosity: 1 
log-queries: yes
log-replies: yes

local-zone: "adserver.example.com" always_nxdomain
local-zone: "adserver1.example.com" always_nxdomain
local-zone: "adserver2.example.com" always_nxdomain
local-zone: "adserver3.example.com" always_nxdomain
local-zone: "1-23a.com" always_nxdomain
local-zone: "1-23b.com" always_nxdomain
local-zone: "1f23b.com" always_nxdomain
local-zone: "12g3.com" always_nxdomain
local-zone: "1g23.com" always_nxdomain
local-zone: "1234.com" always_nxdomain
local-zone: "123a.com" always_nxdomain
local-zone: "12322.com" always_nxdomain

`
@gthess

[gthess]

I still can't reproduce it. I get NXDOMAIN on all those local zones.
Could you try unbound-control list_local_zones on a running Unbound instance and see if you get all your zones (and some more from default configuration) back?
You would need:

remote-control:
    control-enable: yes

in your configuration. If you get an error that remote control is not setup you could run unbound-control-setup to generate the appropriate default keys.