Re: [LUG] Bind zone forwarding

[Simon Waters <Simon@xxxxxxxxxxxxxxxxxxxx>]

Alex Charrett wrote:
> I've got this in my named.conf:
>
> zone "test" IN {
>       type forward;
>       forward only;
>       forwarders { 192.168.10.1; };
> };
>
> Now I'd expect this to forward all queries for the test zone to the
> nameserver 192.168.10.1.  But dig is giving me NXDOMAIN instead. (the
> lookups work when directly pointed at 192.168.10.1 (with dig
> machine.test @192.168.10.1).

forwarding sucks - become a secondary for "test". 

Forwarding make some sense in firewall situations for Internet
resolution (i.e. zone "."), and "forward first" can be a good
performance choice in some cases, but otherwise it is rarely a
good design decision.

> I've spent a fair while in the docs and don't see why this isn't working.

Looks okay to me. I don't usually specify the class in the zone
definition (i.e. drop the IN, it is optional).

Is named-checkconf happy? Any errors on reloading?

Post the cut and paste of the local and remote queries.

Simon

--
The Mailing List for the Devon & Cornwall LUG
Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the
message body to unsubscribe.