Can't access external web space with same extension as our AD name

[Guest]

Q. I am running AD in a Windows 2000 Server environment and I am using the integrated DNS server for internal name resolution and using forwarders to allow access to the internet. This is all working fine apart from one small problem: From computers in the AD I have never been able to access our external web space that uses the same naming convention as our internal name space (The IP address of the external space works so I know this is a DNS related problem). ie. an example of a computer name here is 'pc01.ourcompany.com' while the external web space that is not resolving is 'www.ourcompany.com'

If anyone has a solution for this it would be very much appreciated (I'm really hoping that this is not a problem with the naming convention I have used in that I should have used something different to the registered domain name).

 

[Cary Shultz [A.D. MVP]]

Piers,

This is a common situation. In your DNS MMC simply add a Host Record
called/named 'www' - without the quotes - and enter the Public IP Address of
your web site. This will resolve that issue!

There are people who will tell you that you should use yourcompany.local for
the internal namespace while using yourcompany.com your for external
namespace and there are people who will tell you that have a split brain DNS
namespace is not a problem. I have set up a couple of 'yourdomain.local'
domains and a lot of split-brain DNS domains. There is not really a problem
either way. It *might* be better to use the yourdomain.local /
yourdomain.com namespace from a security point-of-view, however.

HTH,

Cary

Q. I am running AD in a Windows 2000 Server environment and I am using the

integrated DNS server for internal name resolution and using forwarders to
allow access to the internet. This is all working fine apart from one small
problem: From computers in the AD I have never been able to access our
external web space that uses the same naming convention as our internal name
space (The IP address of the external space works so I know this is a DNS
related problem). ie. an example of a computer name here is
'pc01.ourcompany.com' while the external web space that is not resolving is
'www.ourcompany.com'.

If anyone has a solution for this it would be very much appreciated (I'm

really hoping that this is not a problem with the naming convention I have
used in that I should have used something different to the registered domain
name).