Router 192.168.1.254 has 2 DCs, one is an IIS webServer with e2k as well. I can get to the www.domainName.org from everywhere but the server upon which it is running and the other local DC.
Both DCs have their own IP and point to themselves for DNS...
192.168.1.253 = DC (GC...)
DNS = 192.168.1.253
192.168.1.252 = Exchange & WebServer
DNS = 192.168.1.252
Added an alias to both DNS on both DCs for www to point to 192.168.1.252; worked. ;-)
Router 192.168.1.254 has 2 DCs, one is an IIS webServer with e2k as well. I can get to the www.domainName.org from everywhere but the server upon which it is running and the other local DC.
Both DCs have their own IP and point to themselves for DNS...
192.168.1.253 = DC (GC...)
DNS = 192.168.1.253
192.168.1.252 = Exchange & WebServer
DNS = 192.168.1.252
In Stephan Barr <[email protected]> posted a question
Then Kevin replied below:
: Router 192.168.1.254 has 2 DCs, one is an IIS webServer with e2k as
: well. I can get to the www.domainName.org from everywhere but the
: server upon which it is running and the other local DC.
:
: Both DCs have their own IP and point to themselves for DNS...
: 192.168.1.253 = DC (GC...)
: DNS = 192.168.1.253
:
: 192.168.1.252 = Exchange & WebServer
: DNS = 192.168.1.252
:
: Any ideas...?
If you don't have a forward lookup zone for domainName.org you need one,
then add a record named www give it the private IP of the local webserver.
If you have other names such as mail.domainName.org you will need a record
named mail with its IP.