Can't find server name for address 16.153.192.24: No response from server

Kevin Darcy kcd at daimlerchrysler.com
Mon Apr 23 23:56:58 UTC 2001


Looks like your nameserver isn't able to find the CNAME in the
240.153.16.in-addr.arpa zone. Are you sure that that zone is properly delegated
from 153.16.in-addr.arpa or 16.in-addr.arpa? The timeout ("no response from
server") implies that maybe the zone is delegated to nameservers which are
inaccessible to yours.

You could probably kludge around this by defining 240.153.16.in-addr.arpa as
slave/stub/forward on your nameserver, pointing at the master for that zone.
But that's not a general solution, since *other* nameservers will also have
problems resolving addresses in the range, unless the delegations are fixed or
they too are kludged in similar ways.

Also, you appear to have a (possibly related) problem reverse-resolving
16.153.192.24. That's why nslookup is skipping to the second nameserver in your
/etc/resolv.conf. Either use a real lookup tool (like "dig") which doesn't
require reverse-resolution of the nameservers it's using, or arrange to have a
reverse record added for 16.153.192.24, to humor nslookup.


- Kevin

Matt Muggeridge wrote:

> Hi,
> I've implemented RFC 2317 in my 16.153.240/26 network and am having trouble
> with reverse lookups from the primary server - they work fine from the
> parent (secondary) server. I own addresses 64-127.
>
> The primary server is 16.153.192.24 running BIND 8.1.2. The parent (and
> secondary) server is 16.153.192.1 running BIND 4.
>
> When using nslookup on the primary server it times out, then successfully
> fails over to the secondary (parent) server, which can then answer forward
> and reverse queries. When I set the server back to my primary it will answer
> forward queries but not reverse.  What am I missing?
>
> I guess there is something wrong with my implementation of RFC 2317 - but my
> head-scratching, searching this newsgroup, O'Reilly and the RFC hasn't
> helped me.
>
> Here's an example of the failure - running nslookup on the PRIMARY:
>
>     $ nslookup
>     *** Can't find server name for address 16.153.192.24: No response from
> server
>     Default Server: oils.ozy.dec.com
>     Address: 16.153.192.1
>
>     > witch-e0.ucx.ozy.dec.com
>     Server: oils.ozy.dec.com
>     Address: 16.153.192.1
>     Name: witch-e0.ucx.ozy.dec.com
>     Address: 16.153.240.65
>
>     > 16.153.240.65
>     Server: oils.ozy.dec.com
>     Address: 16.153.192.1
>     Name: witch-e0.ucx.ozy.dec.com
>     Address: 16.153.240.65
>     Aliases: 65.240.153.16.in-addr.arpa
>
>     > server kingsx.ozy.dec.com
>     Default Server: kingsx.ozy.dec.com
>     Address: 16.153.192.24
>
>     > witch-e0.ucx.ozy.dec.com
>     Server: kingsx.ozy.dec.com
>     Address: 16.153.192.24
>     Name: witch-e0.ucx.ozy.dec.com
>     Address: 16.153.240.65
>
>     > 16.153.240.65
>     Server: kingsx.ozy.dec.com
>     Address: 16.153.192.24
>     *** kingsx.ozy.dec.com can't find 16.153.240.65: No response from server
>     >
>
> In case it helps, I've extracted the important parts from the various DB
> files.
>
> ---- FILE on PRIMARY: ucx_ozy_dec_com.db ---
>      ;BIND DUMP V8
>      $ORIGIN ozy.dec.com.
>      ucx IN SOA kingsx.ozy.dec.com. POSTMASTER.kingsx.ozy.dec.com. (
>      4 3600 300 172800 43200 ) ;Cl=4
>
>      IN NS kingsx.ozy.dec.com. ;Cl=4
>      IN NS oils.ozy.dec.com. ;Cl=4
>
>      $ORIGIN ucx.ozy.dec.com.
>      witch-e0 IN A 16.153.240.65 ;Cl=4
> ---- end ----
>
> ---- FILE on PRIMARY: 64-127_240_153_16_in-addr_arpa.db ----
>     $ORIGIN 64-127.240.153.16.in-addr.arpa.
>     @ IN SOA kingsx.ozy.dec.com. POSTMASTER.kingsx.ozy.dec.com. (
>     1 3600 300 172800 43200 )
>
>     IN NS kingsx.ozy.dec.com.
>     IN NS oils.ozy.dec.com.
>
>     65 IN PTR witch-e0.ucx.ozy.dec.com.
> ---- end ----
>
> ---- FILE ON PRIMARY: bind.conf ----
>      zone "ucx.ozy.dec.com" in {
>          type master;
>          file "UCX_OZY_DEC_COM.DB";
>          check-names fail;
>          allow-update {
>              localhost;
>              16.153.192.24;
>              16.153.192.83;
>          };
>          allow-transfer { any; };
>      };
>
> zone "64-127.240.153.16.IN-ADDR.ARPA" in {
>     type master;
>     file "64-127_240_153_16_IN-ADDR_ARPA.DB";
>     check-names fail;
>     allow-update {
>         localhost;
>         16.153.192.24;
>         16.153.192.83;
>     };
>     allow-transfer { any; };
> };
>
> ---- FILE on PARENT : host.db ----
>      ; ucx.ozy.dec.com delegated
>      ucx IN NS kingsx.ozy.dec.com.
>      IN NS oils.ozy.dec.com.
> ---- end ----
>
> ---- FILE on PARENT: hosts.rev.240 ----
>      ; RFC 2317 - Classless IN-ADDR.ARPA delegation
>      ;
>      ; Network 16.153.240/26 delegated for range 64-127
>      ;
>      64-127 NS kingsx.ozy.dec.com.
>       NS oils.ozy.dec.com.
>      ;
>      65 IN CNAME 65.64-127.240.153.16.in-addr.arpa.
> ---- end ----
>
> ---- FILE on PARENT: named.boot ----
>      secondary ucx.ozy.dec.com 16.153.192.24 ucx.db
> ---- end ----
>
> ---- DUMP FILE on PARENT: ucx.db ----
>      $ORIGIN ozy.dec.com.
>      ucx IN SOA kingsx.ozy.dec.com. POSTMASTER.kingsx.ozy.dec.com. (
>      4 3600 300 172800 43200 )
>      IN NS kingsx.ozy.dec.com.
>      IN NS oils.ozy.dec.com.
>      $ORIGIN ucx.ozy.dec.com.
>      witch-e0 IN A 16.153.240.65
> ---- end ----
>
> Any ideas much appreciated.
> Matt.





More information about the bind-users mailing list