Solved

CNAMEs all the way?

Posted on 2011-03-10
3
425 Views
Last Modified: 2012-05-11
So I'm not especially happy with my current webhost with whom we have scores of webservers with a managed hardware setup and no control over IP assignment.

Since I won't be able to take out a new supplier and reassign the IPs, I was wondering about the following scenario.

What if rather than pointing my domains to the 'A' records, I set up a bunch of domains e.g. 12-34-56-78.mydomain.com pointing at the infrastructure IPs and then CNAMEd all domains to the relevant IP?

That way I can migrate sites to a new supplier by lowering the TTL on 12-34-56-78.mydomain.com and repointing it to the new supplier.

Will this work? Will I hit problems?
0
Comment
Question by:Borgs8472
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 40

Expert Comment

by:noci
ID: 35109911
That should work. In fact that's the way it should have been setup anyway.
As with every A records there should be a PTR record, and you can have only one PTR record for an address....

0
 
LVL 4

Accepted Solution

by:
Borgs8472 earned 0 total points
ID: 35117665
I've finished my research. Because you can't CNAME the @ record, cunning must be employed.

Given you're running a typically customer1.com, www.customer1.com setup with www.customer1.com being the primary. First off you create a customer1.yourhostingdomain.com address that points to the server where you want it.

Then you CNAME www.customer1.com to customer1.yourhostingdomain.com

Importantly, you must perform the 301 redirect from customer1.com www.customer1.com on a DNS server you control. In my case I've asked in my DNS provider (MelbourneIT) can support this.

If so, DNS setup becomes a little complex as you have to point the A record to your DNS provider (or some other hosting) and CNAME the www record, but after doing so you have full control of where you want to point the website, despite not being the DNS host.

Also, yourhostingdomain.com becomes a single DNS point of failure for your whole operation so it must be highly robust.
0
 
LVL 4

Author Closing Comment

by:Borgs8472
ID: 35154525
Solved own issue
0

Featured Post

Enroll in June's Course of the Month

June’s Course of the Month is now available! Experts Exchange’s Premium Members, Team Accounts, and Qualified Experts have access to a complimentary course each month as part of their membership—an extra way to sharpen your skills and increase training.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Most DNS problems are VERY easily troubleshot and identifiable if you can follow the steps a DNS query takes. I would like to share the step-by-step a DNS query takes from the origin to the destination. _____________________________________________…
I wrote this article to explain some important DNS concepts that should be known to avoid some typical configuration errors I often see in forums. I assume that what is described here is the typical behavior of Microsoft DNS client. I don't know …
Come and listen to Percona CEO Peter Zaitsev discuss what’s new in Percona open source software, including Percona Server for MySQL (https://www.percona.com/software/mysql-database/percona-server) and MongoDB (https://www.percona.com/software/mongo-…
This video Micro Tutorial shows how to password-protect PDF files with free software. Many software products can do this, such as Adobe Acrobat (but not Adobe Reader), Nuance PaperPort, and Nuance Power PDF, but they are not free products. This vide…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question