From: Rob S. <mo...@tu...> - 2010-01-28 23:05:05
|
Stuart Biggerstaff wrote: > > Why is that a CNAME, when they’re different domains? Wouldn’t you just > put a separate A record in each domain pointing to the same IP? > There are specific reasons why you might do that within a corporate network. An example is you have a Web server within a DMZ behind some sort of NAT scheme; let's say it's www.example.com on that outside and that resolves externally to a public address, but internally to a private address. Your internal network has hosts of the variety hostname.sitename.example.com. Now www.example.com on the inside is really webserver.sitename.example.com and your DNS server internally serves up sitename.example.com. Rather than going out the Net, your internal clients will want to to talk webserver.sitename.example.com, but you want to still access via the URL www.example.com, so you just set cname for for www.example.com pointing to webserver.sitename.example.com. Just an example I've seen in umpteen places. Clear as mud, right? |