Internal Domain and External Website resolver issues.

[Mike]

I know this is probably a common problem so I am hoping
there is an easy fix. I just recently aquired W2K domain
called XYZ.com

The problem is that when my clients try to hit our public
facing website (XYZ.com) it cannot resolve the website
because our internal DNS thinks it's our domain controller
because they are the same name.

My DHCP server hands our a primary DNS as a private IP
address (my internal DNS) and the secondary DNS is our
ISP's DNS.

The only work around is to hard code my ISP's DNS as the
primary. But then I run into Cient-Domain communication
issues because my client Laptops don't talk with the
domain controller.

Make sense?

Is there a resolution?

Thanks
Mike

 

[Kevin D. Goodknecht [MVP]]

In

I know this is probably a common problem so I am hoping
there is an easy fix. I just recently aquired W2K domain
called XYZ.com

The problem is that when my clients try to hit our public
facing website (XYZ.com) it cannot resolve the website
because our internal DNS thinks it's our domain controller
because they are the same name.

Add the missing records to the internal DNS zone, use the DNS console expand
the server and forward lookup zones, open the zone for xyz.com, in the
Action menu add new host, name it www give it the IP of the public website.
You cannot access the external website by xyz.com because this requires a
blank (same as parent folder) host which MUST point to the IP address on DCs
that have Client for MS Networks, and File and printer sharing bound. You
need to advise users to use www.xyz.com. Or you can set up IIS on the DCs
with a website that redirects users to www.xyz.com.

My DHCP server hands our a primary DNS as a private IP
address (my internal DNS) and the secondary DNS is our
ISP's DNS.

This is incorrect, you should not use ISP's DNS in ANY position on ANY
domain member.
This will cause many problems and errors.