errors in log file

[Douglas W. Palme]

Sorry I thought the list was still in, but as I see now it wasn't.....


Do I want to use this same format for the inverse?

Douglas


----- Original Message -----
From: "Mathias Körber" <mathias at koerber.org>
To: "Douglas W. Palme" <dpalme at blackcatsolutions.com>; "Mathias Körber"
<mathias at koerber.org>
Sent: Thursday, December 28, 2000 11:58 AM
Subject: RE: errors in log file


> > Can you provide me an example?
>
> Simple:
>
> $TTL 3600
>
> @   IN SOA ns.blackcatsolutions.com. hostmaster.blackcatsolutions.com. (
>      20001228001 ; serial
>      3600  ; refresh
>      900  ; retry
>      43200  ; expire
>      3600 )  ; minimum
>
>     IN NS <your first nameserver serving this zone>
>     IN NS <your second nameserver serving this zone>
>
>     IN PTR whatever.
>
>
>
> >
> > I appreciate you taking the time to help me with this....
>
> No problem, rhough it would have been nicer to leave the list in so that
> others can
> a) benefit
> b) correct me
> c) add to my stuff
> d) comment etc
>
> rgds
>
> >
> > Douglas
> >
> > ----- Original Message -----
> > From: "Mathias Körber" <mathias at koerber.org>
> > To: "Douglas W. Palme" <dpalme at blackcatsolutions.com>; "Mathias Körber"
> > <mathias at koerber.org>
> > Sent: Thursday, December 28, 2000 11:24 AM
> > Subject: RE: errors in log file
> >
> >
> > > > Also I know this is probably a very stupid question on my part, but
a
> > > > question not asked is a question that is stupid....but when
> > you told me
> > I
> > > > should add a $TTL 3600 on the first line..is that on a line just
prior
> > to
> > > > the serial? or before the SOA?
> > >
> > > First line of the zonefile, before the SOA record.
> > >
> > > >
> > > > Douglas
> > > >
> > > > ----- Original Message -----
> > > > From: "Mathias Körber" <mathias at koerber.org>
> > > > To: "Douglas W. Palme" <dpalme at blackcatsolutions.com>;
> > "Mathias Körber"
> > > > <mathias at koerber.org>
> > > > Sent: Thursday, December 28, 2000 11:02 AM
> > > > Subject: RE: errors in log file
> > > >
> > > >
> > > > > > Dec 28 05:43:39 ns named[387]: Forwarding source address is
> > > > [0.0.0.0].1259
> > > > > > Dec 28 05:43:39 ns named[387]: Ready to answer queries.
> > > > > > Dec 28 05:46:07 ns named[387]: reloading nameserver
> > > > > > Dec 28 05:46:07 ns named[387]: Zone
> > > > "226.40.117.216.IN-ADDR.ARPA" (file
> > > > > > 216.117.40.226): No default TTL set using SOA minimum instead
> > > > >
> > > > > This is just a warning. You should put a
> > > > > $TTL 3600
> > > > > before the SOA record (first line of the zonefile)
> > > > >
> > > > > > Dec 28 05:46:07 ns named[387]: Zone
> > > > "226.40.117.216.IN-ADDR.ARPA" (file
> > > > > > 216.117.40.226): no NS RRs found at zone top
> > > > >
> > > > > That is the error I guessed below. You have no NS records in that
> > > > > zonefile! Fix that and the zone should load!
> > > > >
> > > > > > Dec 28 05:46:07 ns named[387]: master zone
> > > > "226.40.117.216.IN-ADDR.ARPA"
> > > > > > (IN) rejected due to errors (serial 2000090201)
> > > > > >
> > > > > > those are the lines just preceding the rejected line....
> > > > > >
> > > > > > Douglas
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "Mathias Körber" <mathias at koerber.org>
> > > > > > To: "D.W." <dpalmeNOSPAM at unitedtraffic.com>;
> > > > > > <comp-protocols-dns-bind at moderators.isc.org>
> > > > > > Sent: Thursday, December 28, 2000 10:06 AM
> > > > > > Subject: RE: errors in log file
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > > We are running bind on a server, and although everything
> > > > seems to=20
> > > > > > > > be working
> > > > > > > > correctly we are getting some errors in the
> > > > /var/log/messages file.
> > > > > > > >=20
> > > > > > > > Here is one of those errors:
> > > > > > > > Dec 28 05:46:07 ns named[387]: master zone =
> > > > > > > "237.40.117.216.IN-ADDR.ARPA"
> > > > > > > > (IN) rejected due to errors (serial 2821358817)
> > > > > > >
> > > > > > > Hmm. There should have been more specific errors before
> > > > this. This is
> > > > =
> > > > > > > just the
> > > > > > > message saying that named encountered too severe errors to
> > > > > > continue with =
> > > > > > > this zone.
> > > > > > > You would need to read/understand and maybe post the
> > > > messages before =
> > > > > > > that.
> > > > > > > >=20
> > > > > > > >=20
> > > > > > > > so I looked at the 216.117.40.237 file and don't see any
> > problems:
> > > > > > > >=20
> > > > > > > > @   IN SOA ns.blackcatsolutions.com.
> > > > > > hostmaster.blackcatsolutions.com. =
> > > > > > > (
> > > > > > > >     20001228001 ; serial
> > > > > > >
> > > > > > > I believe that this serial# is too long for an integer.
> > > > Usually only 2
> > > > =
> > > > > > > digits
> > > > > > > for the daily update (after the YYYMMDD) are used, you have 3
> > (001).
> > > > > > >
> > > > > > > >     3600  ; refresh
> > > > > > > >     900  ; retry
> > > > > > > >     43200  ; expire
> > > > > > >
> > > > > > > This will not likely be the problem, but your expiry time
> > > > is WAY too =
> > > > > > > low.
> > > > > > > Recommended values start at 1 week (I recommend 3-4 weeks, to
> > > > accomodate
> > > > > > > vacationing admins before the zone vanishes from the secondary
=
> > > > > > > nameservers).
> > > > > > >
> > > > > > > >     3600 )  ; minimum
> > > > > > > >=20
> > > > > > > > @   IN PTR first.blackcatsolutions.com.
> > > > > > >
> > > > > > > You don't seem to have any NS records for this zone, which
> > > > is BAD and
> > > > =
> > > > > > > likely
> > > > > > > your error. You will need to put at least 1 NS record to
> > > > make named =
> > > > > > > happy,
> > > > > > > and 2 to satisfy the RFCs (RFC2182 being one of them).
> > > > > > >
> > > > > > >
> > > > > > > >=20
> > > > > > > > If anyone has any suggestions or knows what we may be
> > > > doing wrong=20
> > > > > > > > or need to
> > > > > > > > tweak, I'm all ears.....
> > > > > > >
> > > > > > > More detailed input usually gets you better help, so a
complete
> > list
> > > > of
> > > > > > > error messages for this zone would have avoided my
> > guessing above.
> > > > > > >
> > > > > > > HTH HAHNY
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> >