BIND & Reverse Lookup problems

[Mark.Andrews at nominum.com]

	You ISP has not set up 93.97.209.in-addr.arpa yet.  Both
	of the servers listed are lame.

	To test you should make your server master for
	93.97.209.in-addr.arpa and add the CNAMES pointing into
	1-30.93.97.209.in-addr.arpa.

	When you go into production you should be slaves for
	93.97.209.in-addr.arpa and 92.97.209.in-addr.arpa.  This
	allows you to resolve local addresses when the external
	links are down.

	Also since you are being delegated CIDR blocks from the
	look of the address ranges.  The ranges of the relevent
	blocks are 0-31 and 96-127.  Getting this fixed now may
	advoid some confusion in the future.

	Mark

> Hello everyone,
> For some reason my primary nameserver will not do reverse lookups.  I've
> gone over my db & conf files, but I can't find the problem.  It's
> driving me nuts.  Whenever I attempt to do a reverse lookup I get the
> following standard message.
> 
> *** ns1.signalcore.com can't find 209.97.93.16: Server failed
> 
> Hopefully, you guys can help.  I've included my named.conf file as well
> as my reverse db file for that particular subnet.
> 
> Here's the "named.conf" file:
> 
> options { directory "/var/named"; };
> 
> zone "." {
>         type hint;
>         file "db.cache";
> };
> 
> zone "0.0.127.in-addr.arpa" {
>         type master;
>         file "db.127.0.0";
> };
> 
> zone "signalcore.com" in {
>         type master;
>         file "db.signalcore";
> };
> 
> zone "1-30.93.97.209.in-addr.arpa" in {
>         type master;
>         file "db.209.97.93.1-30";
> };
> 
> zone "96-126.92.97.209.in-addr.arpa" in {
>         type master;
>         file "db.209.97.92.96-126";
> };
> 
> zone "44.227.209.in-addr.arpa" {
>         type master;
>         file "db.209.227.44";
> };
> 
> zone "eliasconsulting.com" {
>         type slave;
>         file "db.eliasconsulting";
>         masters { 209.97.92.3; };
> };
> 
> zone "baseballactivist.com" {
>         type master;
>         file "db.baseballactivist";
> };
> 
> zone "hathathat.com" {
>         type master;
>         file "db.hathathat";
> };
> 
> zone "fosterdog.com" {
>         type master;
>         file "db.fosterdog";
> };
> 
> zone "digi-mon.com" {
>         type master;
>         file "db.digi-mon";
> };
> 
> 
> Here's the "db.209.97.93.1-30" file
> 
> ; $Id: db.209.97.93.1-30,v 1.6 1999/12/30 18:53:04 root Exp $
> @               IN      SOA     ns1.signalcore.com. reuben.spacelab.net.
> (
>                 11              ; serial number
>                 3600            ; refresh
>                 3600            ; retry
>                 604800          ; expire
>                 86400 )         ; TTL
>                 IN      NS      ns1.signalcore.com.
>                 IN      NS      ns2.signalcore.com.
> 1               IN      PTR     redwood-2.signalcore.com.
> 4               IN      PTR     maple.signalcore.com.
> 5               IN      PTR     serrano.signalcore.com.
> 6               IN      PTR     tiny.signalcore.com.
> 7               IN      PTR     pete.signalcore.com.
> 8               IN      PTR     bristlecone.signalcore.com.
> 9               IN      PTR     macadamia.signalcore.com.
> 10              IN      PTR     shon.signalcore.com.
> 11              IN      PTR     ed.signalcore.com.
> 12              IN      PTR     larch.signalcore.com.
> 13              IN      PTR     acacia.signalcore.com.
> 14              IN      PTR     spruce.signalcore.com.
> 16              IN      PTR     palm.signalcore.com.
> 17              IN      PTR     ldap.pace.signalcore.com.
> 18              IN      PTR     www.pace.signalcore.com.
> 19              IN      PTR     mango.signalcore.com.
> 
> I'd appreciate any help you can offer.
> 
> Thanks,
> Reuben
> 
> 
> Sent via Deja.com http://www.deja.com/
> Before you buy.
> 
> 
--
Mark Andrews, Nominum Inc. / Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com