This is a discussion on Re: CNAME and other DATA error in BIND 8.4.4 within the Bind Users forums, part of the DNS and Related Forums category; In article <cia6f1$2kl8$1@sf1.isc.org>, Richard.Zinar@overture.com (Richard Zinar) wrote: > I know ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
In article <cia6f1$2kl8$1@sf1.isc.org>,
Richard.Zinar@overture.com (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: What name has the CNAME conflict? It should be in the log message. > > > $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 ... > > Richard -- Barry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me *** |