>Why is this bad?
It isn't necessarily bad to have a CNAME. The problem is that it can cause
DNS delays, which may outweigh other benefits of the CNAME. The real
question is why do you want www.xidix.com to be a CNAME for xidix.com? If
you don't know the answer, you should just have an A record for www.xidix.com.
>Why would I have one? (I don't manage our DNS, the ISP does.)
The ISP probably uses a "cookie cutter" approach to domains, and
automatically assumes that all domains will have both "www.example.com" and
"example.com" point to the same IP address (the web server). And rather
than give each one an A record, they felt it would be easier to have one of
them a CNAME.
>Why would www.xidix.com have a CName and mail.xidix.com not have one?
Because if mail.xidix.com had a CNAME to xidix.com, then it would point to
the web server.
In your case, the DNS servers are giving out the IP address of your web
server when asked for www.xidix.com, so there won't be any delays in most
cases (modern browsers, for example, won't have a problem) . The real
problem would be if the DNS servers returned the CNAME without an IP
address, which would cause an extra DNS lookup, slowing down the resolution
time.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
