>Hello All,
>    Few days ago, I added two ns entries into my DNS
>cache file,

meaning: db.cache of ISC BIND 8 ?

what brand & version of DNS ? on what platform?

>Since then the DNS server dies after every
>two hour or so, the event log registers the listed
>below event for the DNS server, the whole log file is
>full of such messages. Can anyone please help me how
>to solve this problem.

As always, we'll try.

>;  Database file domain.net.dns for domain.net zone.
>;      Zone version:  22

If you tell me the real name of the domain, I'll run DNS Expert on it and 
send you the report.  But first fix the pb's below in your zone file.

And, for this DNS Expert exercise, if you could, temporarily, on your DNS, 
let me in for zone-transfer by my workstation's ip, in

# file: named.conf

options
{
allow-transfer {212.73.210.79;};
};

Then when we get you sorted out, take my ip address out.

>;

how about adding these two lines at the top of the zone file:

$TTL 86400
$ORIGIN domain.net

>@                       IN  SOA ns1.domain.net. info.domain.net. (
>                                 22          ; serial number
>                                 3600        ; refresh
>                                 600         ; retry
>                                 86400       ; expire
>                                 3600      ) ; minimum TTL

very low TTL in general, most of us run 86400 secs, one day.

I recommend the YYYYMMDDxx for serial number, but it's arbitrary, you know.

>;
>;  Zone NS records
>;
>
>@                       NS      ns1
>@                       NS      ns2

BZZZZ: NS records must point to FQHN, fully qualified host names, so:

@                       NS      ns1.domain.net
@                       NS      ns2.domain.net


>;
>;  Zone records
>;
>
>@                       A       216.247.239.112
>@                       MX      5       mail
>@                       MX      1       mail

BZZZZ:  MX records must point to FQHN, fully qualified host names.

@                       MX      5       mail.domain.net.
@                       MX      1       mail.domain.net.

BZZZZ:  why have you the "mail" host twice?? do you mean mail1 and mail2

>destek                  A       216.247.239.112
>mail                    A       216.247.239.112
>ns2                     A       216.247.239.113
>support                 A       216.247.239.112
>www                     CNAME   @

BZZZZ: I've never seen a @ on the right side!!

just be simple, put this:
www                     A    216.247.239.112

BZZZZ: and where's the A record for "ns1" ??  oops, that's just the 
authoritative nameserver for the domain.

 From www.samspade.org, using rDNS:

Reverse DNS Scan

      216.247.239.1 int-5500.interland.net (bogus rDNS)
      216.247.239.2 int-5500.interland.net (bogus rDNS)
      216.247.239.48 news.boards.ie
      216.247.239.80 esakal.com
      216.247.239.86 mail.admoves.com (bogus rDNS)
      216.247.239.114 atanet.net (forged rDNS)
      216.247.239.134 simpsonsecuritypapers.com
      216.247.239.193 projectnets.com
      216.247.239.208 dedicated.gucciardo (bogus rDNS)

BZZZ:  your .112 and .113 are missing from the reverse zone.  Since many 
mail servers do reverse lookups of mail clients, your mail host @ .112 will 
be rejected as "bad reverse".

"ip block" from  samspade.org

P block lookup for 216.247.239.112

whois -h whois.arin.net 216.247.239

Interland, Inc. (NETBLK-INTERLAND-3) INTERLAND-3 216.247.0.0 - 216.247.255.255
CARNEGIE COMMUNICATIONS (NETBLK-ACUINFOCOM) ACUINFOCOM
                                              216.247.239.224 - 216.247.239.239
galileo development systems (NETBLK-GALCOLOCATED1COM) GALCOLOCATED1COM
                                              216.247.239.240 - 216.247.239.249

If you are not interland, then interland needs to "delegate the reverse 
zone authority" to your DNS.

also, for debugging to the named.run file, I use this. Paste it into your 
named.conf:

/*
logging
{
channel my_file {file "/etc/namedb/named.run"; severity debug; print-time 
yes; };
category default {my_file;};
category panic {my_file;};
category packet {my_file;};
category eventlib {my_file;};
category queries {my_file;};
};
*/

.... and remove the /* comments */ while we fix you up.

Len

Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

Reply via email to