Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, August 15, 2012 2:12 PM
I'm not an expert at DNS. I'm not sure if what I'm trying to do is not allowed or good practice. We recently moved our website to a hosting site. I made a CNAME record to www. Site is up and resolving. The web developer wants the root DNS to resolve to the hosted site as well. I was able to do this as an A record pointing to the www IP before but not as a CNAME.
Before:
For example: contoso.com
(same as parent folder) Host (A) 99.99.99.99
www Host (A) 99.99.99.99
Hosted:
www Alias (CNAME) hosted.com. "Operational"
(same as parent folder) Alias (CNAME) hosted.com. "Error below"
A new record cannot be created. An alias(CNAME) record cannot be added to this DNS name. The DNS name contains records that are incompatable with the CNAME record.
Is there a way to resolve this?
All replies (4)
Wednesday, August 15, 2012 2:20 PM âś…Answered
Rather than trying to create a CNAME for the "root" (same as parent), just create a typical, host (A) record for the (same as parent) and point it to the IP address of your hosted site.
IT Guides and Videos | itgeared.com
Wednesday, August 15, 2012 4:34 PM
I agree with Jorge. You are over-thinking it. And it can't create it because you can only have one for a record. Here's Jorge's blog explaining it:
http://networkadminkb.com/KB/a513/how-to-fix-the-dns-name-contains-records-that-are.aspx
.
Personally, I stay away from CNAMEs, because it can be confusing, and causes a resolution chaing that adds extra resolution steps that must be performed. An A record is a direct, one step resolution.
.
Ace Fekay
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
This post is provided AS-IS with no warranties or guarantees and confers no rights.
Thursday, December 6, 2012 4:48 PM
I agree with Jorge. You are over-thinking it. And it can't create it because you can only have one for a record. Here's Jorge's blog explaining it:
http://networkadminkb.com/KB/a513/how-to-fix-the-dns-name-contains-records-that-are.aspx.
Personally, I stay away from CNAMEs, because it can be confusing, and causes a resolution chaing that adds extra resolution steps that must be performed. An A record is a direct, one step resolution.
.
Ace Fekay
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/This post is provided AS-IS with no warranties or guarantees and confers no rights.
Followup:
My site is hosted on Windows Azure, and the IP changes regularly, so an A record is not a good fit. Is there any way to have both a (same as parent) CNAME and MX? You can do A and MX...
Joe
Friday, December 7, 2012 12:07 AM
Followup:
My site is hosted on Windows Azure, and the IP changes regularly, so an A record is not a good fit. Is there any way to have both a (same as parent) CNAME and MX? You can do A and MX...
Joe
Maybe create a delegation for www (assuming you meant for the www record), and point the NS records to the public NS servers that host that Azure zone. This way it always resolves www.azurewebsite.com by using their DNS and not yours, and if it changes, it will reflect the change automatically.
Ace Fekay
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
This post is provided AS-IS with no warranties or guarantees and confers no rights.