Web site access

  • Thread starter Thread starter Mike W
  • Start date Start date
M

Mike W

We have a server setup with the same FQDN as their web
site. Users inside of the domain cannot access the
external web site. This resolves to the local server.
The web site is hosted by a service has one IP address
for many sites. How can we setup DNS to resolve this
problem. Thanks!
 
In
Mike W said:
We have a server setup with the same FQDN as their web
site. Users inside of the domain cannot access the
external web site. This resolves to the local server.
The web site is hosted by a service has one IP address
for many sites. How can we setup DNS to resolve this
problem. Thanks!
Click to expand...

Easy! Common issue with a "Split Horizon" namespace.

All you do is create a www record under your internal zone, and give it the
external IP address.

:-)

--
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
 
We have done as you have described. The problem is that
the hosting site has one IP address for all of the sites
that they host. So, if we put in the ip address of the
host, it cannot be resolved to the correct site.
 
In
Mike W said:
We have done as you have described. The problem is that
the hosting site has one IP address for all of the sites
that they host. So, if we put in the ip address of the
host, it cannot be resolved to the correct site.
Click to expand...
It is done with host headers, your host record FQDN must match the host
header, but it still uses the same IP address. if you access the site by
www.example.com then in the local example.com forward lookup zone you need a
host record named www with the IP of the Web site. If you can only access
the web site by example.com, that requires a blank host pointing to the IP
of the web site. That will cause a problem on your internal domain, due to
the fact that domain controllers register blank hosts for every IP address
on all NICs on them, which is how the SYSVOL share is found. That is why it
is resolving to the DCs address. You can stop the creation of these blank
hosts but it will cause problems loading Group Policies at
\\example.com\SYSVOL\
Here is the article to stop the creation of these blank records: 295328 -
Private Network Interfaces on a Domain Controller Are Registered in DNS
http://support.microsoft.com/?id=295328&FR=1

But I would recommend your hosting company add a host header for
www.example.com then access by that name or using IIS on the DCs to redirect
to www.example.com.
 
Host headers on the website itself will handle that aspect of the problem. DNS will only resolve the IP address for a given name. That's its only responsibility.
It's then up to the website to determine which page to send the client based on the client's request. In the client's request is the URL of the request. The
website will receive this URL and based on this, can determine which page is to be sent. As long as you resolve to the correct IP for the URL, this should work.

Thank you,
Mike Johnston
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
Mike W said:
We have done as you have described. The problem is that
the hosting site has one IP address for all of the sites
that they host. So, if we put in the ip address of the
host, it cannot be resolved to the correct site.
Click to expand...

Well, you heard everyone. The host header diffrentiates the websites in a
web server. An example of a host header is:
www.domain.com

That sounds too easy, doesn't it? But that;s how it works.



--
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
 
Back
Top