Website issue

[adfreak]

Friend of mine has a Windows 2000 Server running IIS and a website which is
accessible via the internet (www.companyname.com) but will not resolve for
internal employees. His is the set up:

The W2K Server is dual homed with a public NIC and private NIC. This server
hosts the website. This server is also a DNS server (the thing does
everything unfortunately). The public NIC is 67.93.xxx.xxx and the private
is 192.168.1.x. In the DNS server, there is a zone for the comanyname.com
with a WWW cname record with the public address. This is an AD shop and the
AD domain name is companyname.local. Why would internal users being able to
browse www.yahoo.com and not www.companyname.com ? Their DNS settings point
to the private NIC as the primary DNS Server?

Help

 

[Ace Fekay [MVP]]

In

Friend of mine has a Windows 2000 Server running IIS and a website
which is accessible via the internet (www.companyname.com) but will
not resolve for internal employees. His is the set up:

The W2K Server is dual homed with a public NIC and private NIC. This
server hosts the website. This server is also a DNS server (the
thing does everything unfortunately). The public NIC is
67.93.xxx.xxx and the private is 192.168.1.x. In the DNS server,
there is a zone for the comanyname.com with a WWW cname record with
the public address. This is an AD shop and the AD domain name is
companyname.local. Why would internal users being able to browse
www.yahoo.com and not www.companyname.com ? Their DNS settings point
to the private NIC as the primary DNS Server?

Help

You're using the internal DNS as the *primary* DNS server? What's the second
one? Your ISP's? If so, need to remove that and just use the internal DNS.
That's an AD defacto that you can't get around. Use a forwarder for
efficient Internet resolution. THis is a common oversight.

That said, you have a www record with the public IP of this server? The
internal machines cannot get to the website based on the public IP since .
Need to stipulate the private IP.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Kevin D. Goodknecht [MVP]]

In

Friend of mine has a Windows 2000 Server running IIS and a website
which is accessible via the internet (www.companyname.com) but will
not resolve for internal employees. His is the set up:

The W2K Server is dual homed with a public NIC and private NIC. This
server hosts the website. This server is also a DNS server (the
thing does everything unfortunately). The public NIC is
67.93.xxx.xxx and the private is 192.168.1.x. In the DNS server,
there is a zone for the comanyname.com with a WWW cname record with
the public address. This is an AD shop and the AD domain name is
companyname.local. Why would internal users being able to browse
www.yahoo.com and not www.companyname.com ? Their DNS settings point
to the private NIC as the primary DNS Server?

Help

A www CNAME record with the public address?
Delete the www CNAME and make it a host pointing to the IP address that IIS
is listening on..