Forwarding requests for 10.in-addr.arpa

Unbound
1

I seem to be at a loss how to get requests for anything in
10.in-addr.arpa. to end up at some other configured nameserver. Right
now I have
  local-zone: "10.in-addr.arpa." nodefault
and
  stub-zone:
    name: "10.in-addr.arpa."
    stub-host: 10.64.2.1
but requests never end up on the stub-host. If I s/stub/forward/, it's
the same behaviour. What else do I need to configure to make Unbound
actually forward requests for anything in 10.in-addr.arpa. to my
nameserver of choice?

Cheers,

2

What if you add stub-prime: "no" ?

Paul

3

I use a combination of:
local-zone: "7.168.192.in-addr.arpa." transparent
and
stub-zone:
        name: "7.168.192.in-addr.arpa"
        stub-addr: 192.168.107.4

Has worked fine with every version of Unbound (currently using svn
trunk) on several servers.

4

Tested with nodefault instead of transparent - doesn't work here.

Chris

5

Hi,

I seem to be at a loss how to get requests for anything in
10.in-addr.arpa. to end up at some other configured nameserver. Right
now I have
       local-zone: "10.in-addr.arpa." nodefault
and
       stub-zone:
               name: "10.in-addr.arpa."
               stub-host: 10.64.2.1

You mean stub-addr, not stub-host. Now unbound tries to resolve the
domain name '10.64.2.1', but that does not exist.

I use a combination of:
local-zone: "7.168.192.in-addr.arpa." transparent
and
stub-zone:
        name: "7.168.192.in-addr.arpa"
        stub-addr: 192.168.107.4

And you need transparent because 168.192.in-addr.arpa. is blocked by
default and the 7.168.192.in-addr.arpa. locally overrides that default.
A nodefault for the entire 168.192 range would work, but leave the rest
of 168.192 uncovered, so your current setup is best.

Best regards,
   Wouter

6

W.C.A. Wijngaards wrote:

You mean stub-addr, not stub-host. Now unbound tries to resolve the
domain name '10.64.2.1', but that does not exist.

I use a combination of:
local-zone: "7.168.192.in-addr.arpa." transparent
and
stub-zone:
        name: "7.168.192.in-addr.arpa"
        stub-addr: 192.168.107.4

And you need transparent because 168.192.in-addr.arpa. is blocked by
default and the 7.168.192.in-addr.arpa. locally overrides that default.
A nodefault for the entire 168.192 range would work, but leave the rest
of 168.192 uncovered, so your current setup is best.

Thanks all, that worked.

Cheers,