Can't see external website...

[Martin]

I have a Windows 2000 server with 5 clients, and an
internal domain called "mydomain.com". Users inside the
domain can't accsess their outside website who has the
same name as the internal domain. I know I can set up an -
A- record with www and the IP of the outside website, but
it's not possible. The external website share the IP with
several other web sites. Is there an another way to fix
this? Sorry my bad english...

Mvh
Martin

 

[Jeff Cochran]

I have a Windows 2000 server with 5 clients, and an
internal domain called "mydomain.com". Users inside the
domain can't accsess their outside website who has the
same name as the internal domain. I know I can set up an -
A- record with www and the IP of the outside website, but
it's not possible. The external website share the IP with
several other web sites. Is there an another way to fix
this? Sorry my bad english...

You still set up the host record with the outside IP. Shared or not.

Jeff

 

[Lanwench [MVP - Exchange]]

So your external web hosting account doesn't have a static IP?

 

[Ace Fekay [MVP]]

In

I have a Windows 2000 server with 5 clients, and an
internal domain called "mydomain.com". Users inside the
domain can't accsess their outside website who has the
same name as the internal domain. I know I can set up an -
A- record with www and the IP of the outside website, but
it's not possible. The external website share the IP with
several other web sites. Is there an another way to fix
this? Sorry my bad english...

Mvh
Martin

Have you tried the www entry? You can still create the www record, since the
ISP uses hostheaders for their websites, or how else can the different sites
be accessed?

You can also delegate a zone called www under your internal zone and provide
the public nameservers on record. THis way no matter what the IP is or if it
changes, it will resolve it.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[Jonathan de Boyne Pollard]

I have a Windows 2000 server with 5 clients, and aninternal domain called "mydomain.com". Users inside the domain can't accsess their outside website who has the same name as the internal domain.

.... because you haven't populated your internal view DNS database.


I know I can set up an A record with www and the IP of the outside website, but it's not possible.

Yes, it is.


The external website share the IP with several other web sites.

So what?  Are you saying that your web hosting company doesn't know how to make its content HTTP server serve up web pages for a given domain name?  If the web hosting company is worth its salt, I very much doubt that.

 

[Martin]

Ok... Try this: ping www.lyngenplast.com , you will get
an IP who is 195.159.29.93. Then start Internet Explorer
or an other netbrowser, and write this IP in the adress
field. You will get an answer in norwegian that this site
is parked, and there are no homesite at this place.Can I
still use the WWW entry? And what scould I put in there?
The Ip of the external nameserver? Or the WWW adress?
Maybe this is silly questions...

Best Regards
Martin

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Ok... Try this: ping www.lyngenplast.com , you will get
an IP who is 195.159.29.93. Then start Internet Explorer
or an other netbrowser, and write this IP in the adress
field. You will get an answer in norwegian that this site
is parked, and there are no homesite at this place.Can I
still use the WWW entry? And what scould I put in there?
The Ip of the external nameserver? Or the WWW adress?
Maybe this is silly questions...

The reason you don't get your website is because the server uses host
headers. If you want to connect to your website you have to send the host
header name. Create the www record with the IP then run ipconfig /flushdns
to flush the cache and remove the negative answer in the DNS client cache.

 

[Jeff Cochran]

Ok... Try this: ping www.lyngenplast.com , you will get
an IP who is 195.159.29.93. Then start Internet Explorer
or an other netbrowser, and write this IP in the adress
field. You will get an answer in norwegian that this site
is parked, and there are no homesite at this place.Can I
still use the WWW entry?

Sure. Provided your internal workstations point to your internal DNS
for that zone, that's what will resolve. Assuming the web site
actually exists, since the external IP points to a parked address.

And what scould I put in there?

The IP your web site can be access by.

The Ip of the external nameserver? Or the WWW adress?

The web server. Whatever your internal users can access it by.

Maybe this is silly questions...

Not until you learn how DNS works.

Jeff

 

[Ace Fekay [MVP]]

In

Ok... Try this: ping www.lyngenplast.com , you will get
an IP who is 195.159.29.93. Then start Internet Explorer
or an other netbrowser, and write this IP in the adress
field. You will get an answer in norwegian that this site
is parked, and there are no homesite at this place.Can I
still use the WWW entry? And what scould I put in there?
The Ip of the external nameserver? Or the WWW adress?
Maybe this is silly questions...

Best Regards
Martin

Martin, in addition to what we're all telling you, learning how webservers
work will help in understanding what a hostheader is. A webserver can be
accessed by 3 criteria, 1- IP address, 2- port number (default 80, and
understood to use that or you would need to specify the specific port in
your URL the site is using), 3- host header (the actual URL you are
connecting by).

When you access that IP in a URL, you are getting whatever website is
configured as the default site on that webserver, probably that hosting
company's default site, which isn't used. Please ignore that. Many many many
ISPs use hostheaders for webserver access. Some webservers run hundreds of
websites and they ONLY use one IP address. They use the 3rd criteria to
differentiate the websites on the machine. You'll have to ignore what you're
seeing and take our word on it. Just create the www "A" entry, then give it
195.159.29.93 as the IP address and the webserver takes care of the rest. Or
if you want to do the delegation, delegate www and give it the nameservers
addresses autorative for the zone. Either way, it will connect to that IP
and the hostheader will send it to the specific website that's configured to
use that hostheader.

Hope this helps to understand the mechanics of hostheaders:

What Is a Host Header?:
http://www.winnetmag.com/Article/ArticleID/7404/7404.html

IIS TIPS - Host Header - What is it?:
http://msmvps.com/bernard/archive/2004/07/29/10855.aspx

IIS Answers - How to create multiple websites with one IP address:
http://www.iisanswers.com/Top10FAQ/t10-hostheaders.htm

190008 - HOW TO- Use Host Header Names to Host Multiple Sites from One IP
Address in IIS 5.0:
http://support.microsoft.com/default.aspx?scid=kb;en-us;190008

Ace