DNS can not find 1 web site

  • Thread starter Thread starter Kevin Arentsen
  • Start date Start date
K

Kevin Arentsen

Our domain name in Active Directory is yyy.com. We
outsource our web site to a local Internet provider. Our
desktops on the internal network look to the local DNS
(also domain controller) server. The local DNS does have
forwarders setup. All browsing of the Internet works
fine. Internal clients are unable to get to 1 web site.
The yyy.com web site that is outsourced. The only thing I
can think of is that our internal domain is yyy.com and
DNS gets confused with trying to find it. It simply
brings back a "page cannot be displayed" when internat
clients browse yyy.com. Any help is appreciated.

Kevin
 
In
Kevin Arentsen said:
Our domain name in Active Directory is yyy.com. We
outsource our web site to a local Internet provider. Our
desktops on the internal network look to the local DNS
(also domain controller) server. The local DNS does have
forwarders setup. All browsing of the Internet works
fine. Internal clients are unable to get to 1 web site.
The yyy.com web site that is outsourced. The only thing I
can think of is that our internal domain is yyy.com and
DNS gets confused with trying to find it. It simply
brings back a "page cannot be displayed" when internat
clients browse yyy.com. Any help is appreciated.

Kevin
Click to expand...

Add a new host to your internal yyy.com Forward Lookup Zone named www and
give it the IP of your outsourced web site.

You will have a problem if you want to access it by yyy.com without the www
because Domain Controllers will create a blank record for each of its IP
addresses. The blank record is needed to access you web site not using the
www host name. Your DC needs the blank host for Group Policies.
 
Just to add if they are hosting a ftp site for you you will have to add the
FTP record as well
 
The internal DNS server thinks it's authoritative for the DNS name yyy.com. It will not forward requests for this domain to other servers since it thinks it knows all
the records for this zone. To fix this, simply create a record for the website and point it to the proper address. You can name it whatever you like though the
most common is "www". If you need the website to resolve via the name "yyy.com", this could be a problem since the Active Directory uses this name to
signify domain controllers. You will have to specify a host name for the record.

Thank you,
Mike Johnston[MSFT]
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
In Michael Johnston [MSFT] <[email protected]> posted their
thoughts, then I offered mine
You can name it whatever you like though the
most common is "www". If you need the website to resolve via the
name "yyy.com", this could be a problem since the Active Directory
uses this name to
signify domain controllers. You will have to specify a host name for
the record.
Click to expand...

Michael,

There's actually a really easy registry entry to overcome this behavior of
needing to get to http://yyy.com (without the www in front of it). If
interested, post back and I will post the method.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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