Usually, when Robbie says something I listen. But, on this, I am not so sure. Granted, I haven't read what you said he said, but if he did say that indeed, then I would like to reserve judgment until I've seen proof of the efficacy of this proposal.
My reservation will be mostly borne out of this question:
How is this different from simply creating an A record called root.com and pointing it to the IP address of the web server?
Exactly! That's a no-no! And I want to say that since there is no difference (IMO), then the CNAME trickery would be a no-no too. It doesn't remove the very real possibility that AD-specific record lookups and registration will be routed to the web server at the other end of the http://www.root.com/ record.
Sincerely,
D�j� Ak�m�l�f�, MCSE MCSA MCP+I
D�j� Ak�m�l�f�, MCSE MCSA MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon
From: [EMAIL PROTECTED]
Sent: Thu 9/30/2004 6:40 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] root domain alias
Hey guys…
I was reading Robbie’s DNS book and came across something about using a cname record to designate something like root.com to point to a www record so that if you have the same root domain name as your internal/external website name, then users can use just root.com instead of www.root.com to get to the site.
Curious if anyone has done this… and if they’ve seen any issues with it?
