trying to configure forwarding
Kevin Darcy
kcd at daimlerchrysler.com
Tue Jan 24 00:38:19 UTC 2006
Mikhail T. wrote:
>Hello!
>
>I'm trying to write my own little name-server program. It seems to work
>for local clients (tested by binding it to 127.0.0.2), and I'd like to
>test it from the Internet.
>
>Trouble is, I already run bind9 on my only public-IP and can not afford
>to bring it down for long.
>
>So I decided to use the "type forward", so that only queries about the
>particular test sub-zone (say, T.my.domain), are forwarded by named to
>my server.
>
>Here are the two zones as configured on my machine:
>
> [...]
> zone "my.domain" {
> type slave;
> file "slave/my.domain";
> masters {
> 151.204.231.237;
> };
> };
>
> zone "T.my.domain" {
> type forward;
> forwarders {
> 127.0.0.2;
> };
> forward only;
> };
> [...]
>
>Here is T's entry in the my.domain's zone file:
>
> T 8640 IN NS aldan.algebra.com.
>
>Unfortunately, when I try to `nslookup something.T.my.domain', my
>little daemon does not get the query, but the main one on my machine
>responds with `Non-existent host/domain'.
>
Did your "little daemon" give an NXDOMAIN or a NODATA (i.e. 0 records in
the Answer Section) response for T.my.domain at some point? If so, then
that will cause named to create a negative cache entry for that name,
and it will respond appropriately, without contacting the delegated
nameserver, until that negative cache entry expires.
Also, you should double-check that the delegation was made properly. The
text you quote above _should_ have done the trick, but only if your
origin happened to be my.domain at that point in the zone file. To tell
for sure, do a zone transfer of my.domain and verify that there is a
delegation NS record for T.my.domain.
- Kevin
More information about the bind-users
mailing list