One IP address two web site

Browser shows the same name even domain name portions of URLs differ

[dim44]

My company uses one IP address to host two web sites, let say www.domain_1.com and www.domain_2.com. They are in two different languages and completely independent in terms of content.

I've been analyzing two web sites and found a strange thing.

Let say, there are two home pages:

[domain_1.com...]
[domain_2.com...]

The strange thing is when I replace domain portion of URL like:

[domain_2.com...] - (replaced "domain_1" with "domain_2") I get the same page as I used "domain_1".

I am not a DNS guru. Any help in explanation of how it happens greatly appreciated.

Thanks

[webfoo]

That's probably because they are on the same server. I'm no expert on this either, but my gut feel is that you would need to set a different root folder for each site.

[daveVk]

This is not a DNS issue both domains correctly point to the same IP.

As webfoo says it is to do with server configuration. Check if [domain_1.com...] and [domain_2.com...] without any file or path give the same page, also check if any redirection is happening that is when you enter say [domain_1.com...] does it stay as [domain_1.com...] or something else.

Do you know what kind of web server it is, apache ?

[himalayaswater]

You need to set different webroots / documentroot for each domain. This is also known as virtual hosting under IIS / Apache.

[dim44]

Hi,

Thanks for your responses.

If I type [domain_1...] I get redirect to the [domain_1...] and so on to the home page. If I replace domain_1 with domain_2 and do not change folder 's path I get the same page.

If I type [domain_1...] and domain_2 I get two distinct pages which belong to the corresponding domains.

Ip address is the same for two domains.

[webfoo]

Is this actually a problem, or is it just an annoying nag you can't figure out?

[dim44]

Webfoo, I believe this is a potential problem for our web sites. I want to escalate this case to my boss but without understanding the matter it will be difficult to be persuasive.
I am not in charge for web server configuration but I saw the issue and when posting I believed that it would be a simple answer to it. I see now that I need more info about server’s setting.

Thanks everybody

[wheel]

Himalayswater is correct - it's an apache config problem. It may be the document root, could be something else,but it's certainly in that neighbourhood - likely in httpd.conf.