Even with a minimal zone file, I still see errors, and the zone fails
to load:

$TTL 3600

@ IN SOA ns1.overture.com. dns-admin@overture.com. (
2004033100 ;
10800 ;
3600 ;
604800 ;
86400 ) ; line 9

IN MX 10 mx1.overture.com. ; line 11
IN MX 20 mx2.overture.com.

IN NS ns1.overture.com. ; line 14
IN NS ns02.overture.com.

localhost IN A 127.0.0.1

The log file messages are:

Sep 15 23:03:03 oxygen named[24748]: [ID 295310 daemon.warning] tw.overture.com:
14:tw.overture.com: CNAME and OTHER data error
Sep 15 23:03:03 oxygen named[24748]: [ID 295310 daemon.warning] tw.overture.com:
11:tw.overture.com: CNAME and OTHER data error
Sep 15 23:03:03 oxygen named[24748]: [ID 295310 daemon.warning] tw.overture.com:
9:tw.overture.com: CNAME and OTHER data error
Sep 15 23:03:03 oxygen named[24748]: [ID 295310 daemon.error] master zone "tw.ov
erture.com" (IN) rejected due to errors (serial 2004033100)

Perhaps something in the preceding zone files is triggering this, as
Mark Andrews indicated. I'll have to keep digging. If anyone knows
a good way to debug this (we have 100+ zone files), let me know. Thanks ...

-Richard






Mark Andrews wrote in message news:...
> > Richard Zinar wrote:
> > > I know the standard reason for this error, but I can't see any reason
> > > it should be triggered by the
> > > following zone file:

> >
> >
> > > $TTL 3600

>
> > > @ IN SOA ns1.overture.com.
> > > dns-admin.overture.com. (
> > > 2004032900 ; Serial (YYYYMMDDNN)
> > > 10800 ; refresh period
> > > 3600 ; retry refresh this often
> > > 604800 ; expiration period
> > > 86400 ) ; minimum TTL

>
> > > MX 10 mx1.overture.com.
> > > MX 20 mx2.overture.com.
> > > NS ns1.overture.com.
> > > NS ns02.overture.com.

> >
> >
> > > localhost IN A 127.0.0.1
> > > inventory IN CNAME redir.overture.com.

>
> > > www IN CNAME www.overture.com.

>
> > > @ IN A 61.213.167.165

>
> > > dtc IN CNAME redir.overture.com.

>
> > > cms MX 20 mx1.overture.com.
> > > MX 10 mx2.overture.com.

>
> > > The corresponding named.conf entry is:

>
> > > zone "tw.overture.com" {
> > > type master;
> > > file "tw.overture.com";
> > > };

>
> > > The DNS server is BIND 8.4.4 running on Solaris 8. Is there some
> > > compile option
> > > or named.conf option which might trigger this behavior, or am I
> > > overlooking something
> > > obvious. The file above is the entire zone file. Thanks ...

> >
> > There is no cnme conflict here :
> > > named-checkzone tw.overture.com. x

> > zone overture.com/IN: loaded serial 2004032900
> > OK
> > (where the above zonefile is saved in file x (
> >
> > Are you running chrooted and editing the wrong file ?
> >
> > A comment :
> > you are using a default TTL of 1h but negative cache of 24h . Is that
> > really your intention or have you got that backwards ?
> >
> >
> > > Richard

> >
> >
> > --
> > Peter Håkanson
> > IPSec Sverige ( At Gothenburg Riverside )
> > Sorry about my e-mail address, but i'm trying to keep spam out,
> > remove "icke-reklam" if you feel for mailing me. Thanx.

>
>
> BIND 8 uses a single database. Records from other zones can
> also cause CNAME and other data errors.