Mailing List Archive: Apache: Users

unique virtual server

Index | Next | Previous | View Threaded

bashiro at myway

Apr 26, 2012, 1:45 PM

Post #1 of 3 (212 views)
Permalink

unique virtual server

Hello,

I have two virtual servers that work very fine using a dynamic dns service on port 80.
Now I bought myself a Seagate NAS that also uses a dynamic services from Seagate to access files remotely.
My problem is: The Seagate NAS have a local IP 192.168....

I configured the next virtual host like this;

<VirtualHost 192.168...>
ServerName name.seagateshare.com
DocumentRoot 192.168....
</VirtualHost>

When browser access name.seagate.com, it goes directly to the dynamic dns services and not the seagate.

How do I correct this ?

Best regards
bashiro

Bashiro
Drammen-Norway

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe [at] httpd
For additional commands, e-mail: users-help [at] httpd

yehuda at ymkatz

Apr 26, 2012, 2:28 PM

Post #2 of 3 (204 views)
Permalink

Re: unique virtual server [In reply to]

On Thu, Apr 26, 2012 at 4:45 PM, Bashiro <bashiro [at] myway> wrote:

> My problem is: The Seagate NAS have a local IP 192.168....
>
> I configured the next virtual host like this;
>
> <VirtualHost 192.168...>
> ServerName name.seagateshare.com
> DocumentRoot 192.168....
> </VirtualHost>
>
> When browser access name.seagate.com, it goes directly to the dynamic dns
> services and not the seagate.
>

Just creating a VirtualHost in the Apache configuration will not cause
browsers to go to it.
You need to supply more information about what you are trying to accomplish.

- Y

rshuvalov at hotmail

Apr 27, 2012, 12:03 AM

Post #3 of 3 (199 views)
Permalink

RE: unique virtual server [In reply to]

Hi, Y,

Why your ServerName value in <VirtualHost> section is different from the one
you navigate to ( <http://name.seagateshare.com> name.seagateshare.com vs.
<http://name.seagate.com> name.seagate.com)?

Roman.

From: Yehuda Katz [mailto:yehuda [at] ymkatz]
Sent: Friday, April 27, 2012 1:28 AM
To: users [at] httpd
Subject: Re: [users [at] http] unique virtual server

On Thu, Apr 26, 2012 at 4:45 PM, Bashiro <bashiro [at] myway> wrote:

My problem is: The Seagate NAS have a local IP 192.168....

I configured the next virtual host like this;

<VirtualHost 192.168...>
ServerName name.seagateshare.com
DocumentRoot 192.168....
</VirtualHost>

When browser access name.seagate.com, it goes directly to the dynamic dns
services and not the seagate.

Just creating a VirtualHost in the Apache configuration will not cause
browsers to go to it.

You need to supply more information about what you are trying to accomplish.

- Y

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads