I'm NOT a DNS guru, so perhaps I shouldn't be answering. But, you know I like to talk. I think that typically when people name their AD domains with a .com (as opposed to a .local or some other non-Internet extension), you have to create a host with a name of WWW with your site's IP address. (Assuming your site uses www. as a subdomain). It seems as though from what you're asking, company abc would have the same problems as company xyz. Can abc currently get to the Web site just by going to abc.com? I'd think that would resolve to the DC, not the IIS server, internal or external. Ray at work ________________________________ From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Bill Beckett Sent: Friday, June 18, 2004 8:39 AM To: 'windows2000@xxxxxxxxxxxxx' Subject: [windows2000] DNS Calling all DNS gurus... Question for a hypothetical situation. Suppose there was a company called abc.com and they owned a domain called abc.com. This company had several branch offices all physically connected and they used the abc.com name. Now suppose abc bought a company called xyz, who owned the xyz.com domain name. XYZ wanted to remain on a different network and not be physically connected to abc company like the branch offices were. However, xyz company did want to change their domain name to a sub domain name of abc....let's say na.abc.com. Now my question...internally on the xyz network, aren't the clients going to have a problem if their domain name is now na.abc.com and they try to get out to the domain name of abc.com? (Web site, etc.) ******************************************************** This Weeks Sponsor StressedPuppy.com Games Feeling stressed out? Check out our games to relieve your stress. http://www.StressedPuppy.com ******************************************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm