bind9 - How to set up conditional forwarder for .local domain?

roe-dk · 04-28-2017, 09:01 PM

I can't really figure out what I'm doing wrong here, or if some sort of black magic is required to set up a conditional forwarder for a .local domain.

The setup is as follows:

Debian running bind9.....->.....Win2008R2 DNS.....->.....Google DNS
192.168.0.1/24..................192.168.10.1/24..........8.8.8.8
mydomain.local..................2nddomain.local
................................3rddomain.com

named.conf.options on the Debian is set up to use the Windows as forwarder:

Code:

forwarders {
   192.168.10.1;
};

So one would think any request not pertaining to mydomain.local would be forwarded to 192.168.10.1
But looking at the cached lookups on the Windows box I can see that they are for all other domains than 2nddomain.local

I've tried adding a conditional forwarder specifically for 2nddomain.local in named.conf.local:

Code:

zone "2nddomain.local" {
   type forward;
   forwarders {192.168.10.1;};
};

But no luck.

nslookup against the Debian:

Code:

root@myserver:/etc/bind# nslookup
> server 192.168.0.1
Default server: 192.168.0.1
Address: 192.168.0.1#53
> host.2nddomain.local
Server:         192.168.0.1
Address:        192.168.0.1#53

** server can't find host.2nddomain.local: NXDOMAIN
>

nslookup against the Windows DNS:

Code:

root@myserver:/etc/bind# nslookup
> server 192.168.10.1
Default server: 192.168.10.1
Address: 192.168.10.1#53
> host.2nddomain.local
Server:         192.168.10.1
Address:        192.168.10.1#53

host.2nddomain.local     canonical name = host2.2nddomain.local.
Name:   host2.2nddomain.local
Address: 192.168.10.153
>

Any particular configuration needed to make forwarders work for .local domains?
3rddomain.com, .org, .net or any other public TLD work fine.
Clients using the Debian bind server can also easily resolve hosts directly in the mydomain.local domain.

Any tips?

bathory · 04-30-2017, 03:53 AM

Hi,

Is your debian box authoritative for the whole .local zone, or just mydomain.local? For the latter you should not have any problem, but you should remove the forwarders clause.

Anyway, you should post the zonefile(s) and maybe the config file(s) too, so we could understand your setup.

If debian is authoritative for the whole .local, then ditch also the the definition of 2nddomain.local as a forward zone and use $ORIGIN to define a different NS for 2nddomain.local:

Code:

<- Usual zonefile stuff like SOA etc->
$ORIGIN mydomain.local.
@          NS debian.mydomain.local.
debian A 192.168.0.1

$ORIGIN 2nddomain.local.
@          NS windoze.box.