Trouble configuring forwarders for reverse zones.

[M-lists]

Thanks Chris.

I had actually tried that, but it turned out Windows wasn't answering
reverse queries properly so I didn't notice when I had got it right.  Once
your post pointed out that was the way to go, I got Wireshark on it and
quickly noticed Windows was also at fault.

One further thing, I'll be moving things around on our network soon, and
this means we'll have a classless subnet soon.  So if we moved one of our
Windows subnets to 10.1.1.0/24, how would I forward reverse queries for this
subnet to say 10.1.1.1?

Thanks.


C.


-----Original Message-----
From: Chris Buxton [mailto:cbuxton at menandmice.com] 
Sent: 07 April 2009 17:15
To: Callum Millard
Cc: bind-users at lists.isc.org
Subject: Re: Trouble configuring forwarders for reverse zones.

On Apr 7, 2009, at 8:37 AM, Callum Millard wrote:
> //I've tried a variety of versions of this next line:
> //zone "16/0.0.5.10.in-addr.arpa."
> //zone "5.10.in-addr.arpa."
> //zone "0.0.5.10.in-addr.arpa."
> //Etc., etc.
> zone "16/0.0.5.10.in-addr.arpa." IN {
>
>        type forward;
> 	forwarders {10.5.0.1;};
> };
>
> zone "16/0.0.6.10.in-addr.arpa." IN {
>
>        type forward;
> 	forwarders {10.6.0.1;};
> };

Close, but no cigar. Here is the correct syntax:

zone "5.10.in-addr.arpa." IN {

        type forward;
	forwarders {10.5.0.1;};
};

zone "6.10.in-addr.arpa." IN {

        type forward;
	forwarders {10.6.0.1;};
};

Chris Buxton
Professional Services
Men & Mice