duplicate domain names

[MattH]

We have a web server that runs off site that is the same
name as our domain name. It has a different IP address
than the private network.
If i set up Forwarders on the DNS servers, and give
clients the IPs of these DNS servers, they are able to
browse all of the internet, except our domain's websites,
because it resolves the domain suffix (domain.com) to the
private network (rather than the ip of the webserver
offsite). Is there a way to configure so that if our
private network browses www.domain.com, it resolves the
webserver, and all others (computer.domain.com)resolve to
the private network?

 

[Kevin D. Goodknecht [MVP]]

In

We have a web server that runs off site that is the same
name as our domain name. It has a different IP address
than the private network.
If i set up Forwarders on the DNS servers, and give
clients the IPs of these DNS servers, they are able to
browse all of the internet, except our domain's websites,
because it resolves the domain suffix (domain.com) to the
private network (rather than the ip of the webserver
offsite). Is there a way to configure so that if our
private network browses www.domain.com, it resolves the
webserver, and all others (computer.domain.com)resolve to
the private network?

You need to add the records from your public domain to the private domain,
i.e. www, mail and ftp. This works for all site except the ones that just
use the domain name "domain.com" that name MUST resolve to all IP addresses
on all domain controllers that have file sharing.
The best work around for this is to only access your website by www or set
up IIS on all the domain controllers with a website at "domain.com" and
redirect it to www.domain.com.
If you configure the domain name to resolve to the webserver IP then all
machines will look for the DFS share on the webserver and you will get
userenv errors and replication could also fail.