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:[email protected]] 
Sent: Friday, April 27, 2012 1:28 AM
To: [email protected]
Subject: Re: [users@httpd] unique virtual server

 

On Thu, Apr 26, 2012 at 4:45 PM, Bashiro <[email protected]> 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

Reply via email to