Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a reseller host the sites of my clients are hosted.

One such customer wants to keep the DNS management with them. For this, they request the CNAME for them to do the following change in DNS:


The question is, what the difference is to change the A record pointing to the IP of my server to change the CNAME (As listed above?)

share|improve this question
up vote 2 down vote accepted

There are two differences:

  1. With the CNAME, people trying to access their web page will have to do an extra DNS lookup. This may result in slightly slower "first page" times. (It also adds an additional potential point of failure if they aren't good at managing their DNS.)

  2. With the CNAME, they'll be able to change what IP address the www host points to without having to modify the entry in that domain.

share|improve this answer
xyz is a subdomain of, I would have to be the owner of as possible for this to be correct? – Ridermansb Apr 24 '12 at 15:19
Or you'd have to be coordinating with Because of Host headers, HTTP usually won't "just work" if you redirect your DNS to point to a stranger's server. – David Schwartz Apr 24 '12 at 15:21
Sorry, I missed the part of "you'd have to be coordinating with" which means coordinating?? – Ridermansb Apr 24 '12 at 15:25
Working together. If you just make a CNAME for, say,, it may or may not work. – David Schwartz Apr 24 '12 at 15:26

The is no difference. But the CNAME is easier, because you change just one record. In any case you can say that it's the same.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.