In MikeS <
[email protected]> posted a question
Then Kevin replied below:
: On Win2k server, my local domain is xxxxx.com. My website is now
: hosted at my ISP. How can I get DNS to pass on the URL to external
: site instead of resolving it locally (and of course, unable to
: display the site)?
The best way I've found to resolve this issue is to access the name
internally by
www.xxxxx.com. You can easily add a host record named www
pointing to the IP of the remote website. If you still must get access by
xxxxx.com then you can run IIS on all DCs with a website for xxxxx.com then
on the Home Directory tab redirect it to
www.xxxxx.com. The reason this is
necessary is that Domain controllers create Blank (same as parent folder)
host for every IP address on them. This record is needed to resolve to the
DC's interface that has file sharing bound to it. This is so the SYSVOL DFS
share can be found so group policies can be applied and the domain DFS share
can properly replicate. The GPOs are in the domain DFS share at
\\xxxxx.com\SYSVOL\xxxxx.com\policies If you replace the DCs blank record
with one that points to a web server instead of a DC, then machines will
look to the webserver for the DFS share, which of course won't be there.
