"Steve Z via WinServerKB.com" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We are unable to access company website inhouse through server 2003
network.
> No problem from an outside connection.
> I believe the problem lies with naming the new network domain the same as
our
> website domain name - pilgrimsne.com
> We were under the assumption that server 2003 required this type of domain
> naming convention during the setup of the new server and network. Was this
> correct to assume?
No the opposite is true. Those FQDNs are two different things and exist for
two different reasons,...they should not be the same name. But you are
stuck with it now,...or I should say that it can be a real big hassle to
change it now anyway.
Two things you can do and keep it like it is would be:
1. The first option is to give your internal AD/DNS "static" entries for the
external Hosts so that they resolve properly to the correct external
numbers. All your machines,..every one of them,..needs to use only the
AD/DNS and none other,...the AD/DNS then uses your ISPs DNS in the, ... DNS
Properties--->Forwarders List.
2. The other option is called Split DNS. This article should help.
[Those are underscores, not spaces between the words]
You Need to Create a Split DNS!
http://www.isaserver.org/tutorials/Y...Split_DNS.html
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html
Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------
Similar Threads
Linear Mode
