DNS versus Domain names and Domain controllers

[Bert]

G'day folks,

I've got a bit of a problem here that I'm hoping you can
help me out with regarding the names of Windows 2000
domains versus the naming of internet domains.

The situation is this: Back before I started with the
company I'm working for, they installed their first
Windows2000 domain controller, and had it set up so that
the server believed that their internal LAN network domain
was "torlys.com". This domain controller also provides DNS
resolution for internet sites for all of the company's
internet surfing.

Recently, the company has had a website set up outside our
LAN with a 3rd-Party ISP. The ISP has set up the website
as "torlys.com" as well. Now whenever people on the LAN
try to surf to "torlys.com" they get DNS error messages
because we're not running web-servers or hosting anything
on the domain controller. After testing, I've found that
by pointing all DHCP clients to the 3rd-party ISP's DNS
servers for name resolution solves this problem.

Is there a way (short of reinstalling the Domain ) to stop
the domain controller from referring browsers to itself
for "torlys.com"?

If it does come down to having to reinstall the domain
controller, is there a way to retain all the user accounts
that we've got set up, or are we stuck with doing it all
over again? I'm still not as familiar with Active
Directory as I'd like, and the hits I'm getting from the
online knowledge base aren't being very helpful.

Thanks in advance and best regards,

Bert Van Vliet
MCSE, MCP

 

[Brendon Rogers]

Simply create entries for the torlys.com website etc on your internal DNS
servers. Then when an internal client queries your internal DNS server for
www.torlys.com it will issue it with the external IP address.

In order for W2K AD to work properly the clients (and servers) must talk to
a properly configured DNS. Your ISP's DNS servers are not suitable for this.

 

[Bert V.V.]

Howdy!

-----Original Message-----
Simply create entries for the torlys.com website etc on
your internal DNS servers. Then when an internal client
queries your internal DNS server for www.torlys.com it
will issue it with the external IP address.

Well, now I feel sheepish - I should've known it'd be
something simple that I overlooked. *sigh* Thanks.

In order for W2K AD to work properly the clients (and
servers) must talk to a properly configured DNS. Your
ISP's DNS servers are not suitable for this.

I knew that this was going to happen, but at the time, I
just wanted to get certain departments connected to the
company website and out of my hair. Switching the DNS
servers bought me some time.

Thanks again!

Regards,

Bert Van Vliet,
MCSE, MCP

 

[Jonathan de Boyne Pollard]

B> Recently, the company has had a website set up outside our
B> LAN with a 3rd-Party ISP. The ISP has set up the website
B> as "torlys.com" as well.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-split-horizon-common-server-names.html>