• Sign in to Neowin Faster!

    Create an account on Neowin to contribute and support the site.

  • 0

webmin: Handles the name-based server www.my-domain.org on address *.

Question

tarifa    0

 hello dear all - 

 

on webmin -  i have on a freshly created vhost i have  the following 
   
the phrase is like so:  

Handles the name-based server www.my-domain.org on address *.

 

what makes me wonder is why do we have 

.... address *.


look forward to hear from you 

 

Share this post


Link to post
Share on other sites

7 answers to this question

Recommended Posts

  • 0
tarifa    0

updates: 

 

see the directives

 



DocumentRoot "/sites/www.my_domain.org"        /usr/local/apache/conf/vhost/vhost.conf (67)
ServerName www.my_domain.org                   /usr/local/apache/conf/vhost/vhost.conf (68)
<Directory "/sites/www.my_domain.org">
 allow from all                               /usr/local/apache/conf/vhost/vhost.conf (70)
 Options None                                 /usr/local/apache/conf/vhost/vhost.conf (71)
 Require all granted                          /usr/local/apache/conf/vhost/vhost.conf (72)
</Directory>

 

Share this post


Link to post
Share on other sites
  • 0
tarifa    0


guess: *. seems to be correkt, * notes - all adresses, the point notes the end of the term in the handle.

 

 

see the directives: 

 

DocumentRoot "/sites/www.my_domain.org" /usr/local/apache/conf/vhost/vhost.conf (67)

ServerName www.my_domain.org /usr/local/apache/conf/vhost/vhost.conf (68)

<Directory "/sites/www.my_domain.org">

allow from all /usr/local/apache/conf/vhost/vhost.conf (70)

Options None /usr/local/apache/conf/vhost/vhost.conf (71)

Require all granted /usr/local/apache/conf/vhost/vhost.conf (72)

</Directory>

 

 

 

in other cases it looks like so

 

Quote

  


Handles the name-based server www.the_domain_.org on all addresses

 

- on all adresses!? 

 

this is different


 

update: 


 runned a ping test 
sent 10 ICMP-Pakets to the server

result: - invalid host.

 

Edited by tarifa

Share this post


Link to post
Share on other sites
  • 0
tarifa    0

update: 


guess that all depends on the  NS-Server  entries:

all seems that the Vhost creation process went well and the vhost looks "healthy" 

now i guess that i have to look for the entries regarding the NS-Server. 

what do you suggest - which tests to run - which measures to test!?

Share this post


Link to post
Share on other sites
  • 0
DaveLegg    1,014
16 hours ago, tarifa said:

what makes me wonder is why do we have 


.... address *.


look forward to hear from you 

 

Been a while since I've used Webmin, but at a guess, that's referring to IP addresses. You could have multiple public IPs assigned to your server, say 1.2.3.4, 1.2.3.5, 1.2.3.6 and so on. With this setting, you could connect to the server on any of those IP addresses, request the site, and you'd get it. If you bound the site to a specific IP address, say 1.2.3.4, then you could connect using that IP, request the site, and the server would return it, but if you connected to say 1.2.3.5 and requested the site, the server would give you a 404

  • Like 1

Share this post


Link to post
Share on other sites
  • 0
tarifa    0
7 hours ago, DaveLegg said:

hello dear DaveLegg many thanks for the quick reply and for shaging your ideas and insights. This is very very helpful

 

 

7 hours ago, DaveLegg said:

Been a while since I've used Webmin, but at a guess, that's referring to IP addresses. You could have multiple public IPs assigned to your server, say 1.2.3.4, 1.2.3.5, 1.2.3.6 and so on. With this setting, you could connect to the server on any of those IP addresses, request the site, and you'd get it. If you bound the site to a specific IP address, say 1.2.3.4, then you could connect using that IP, request the site, and the server would return it, but if you connected to say 1.2.3.5 and requested the site, the server would give you a 404

 

....afaik is my directive a broken dirctive which does not function and will stop the system from resolving the process. 


so - as far as i unserstand this all - i should write the directive to

.*. or to to *

to

 

.*

 

this one is weird - and i think that i have to change this

 

<VirtualHost *.>

 

 

https://httpd.apache.org/docs/2.2/mod/core.html#virtualhost

 

<VirtualHost> und </VirtualHost> werden dazu verwendet, eine Gruppe von Direktiven zusammenzufassen, die nur auf einen bestimmten virtuellen Host angewendet werden. Jede Direktive, die im Virtual-Host-Kontext zulässig ist, kann verwendet werden. Wenn der Server eine Anfrage für ein bestimmtes Dokument eines bestimmten virtuellen Hosts empfängt, dann benutzt er die im <VirtualHost>-Container enthaltenen Konfigurationsanweisungen. Adresse kann sein:

Die IP-Adresse des virtuellen Hosts.

 

Ein voll qualifizierter Domainname für die IP-Adresse des virtuellen Hosts. Das Zeichen *, welches nur in Kombination mit NameVirtualHost * verwendet wird, um allen IP-Adressen zu entsprechen. Die Zeichenkette _default_, die nur mit IP-basierten virtuellen Hosts verwendet wird, um nicht zugewiesene IP-Adressen aufzufangen.

 

example.

<VirtualHost 10.1.2.3>
ServerAdmin webmaster@host.foo.com
DocumentRoot /www/docs/host.foo.com
ServerName host.foo.com
ErrorLog logs/host.foo.com-error_log
TransferLog logs/host.foo.com-access_log
</VirtualHost>


VirtualHost Examples 

This document attempts to answer the commonly-asked questions about setting up virtual hosts. These scenarios are those involving multiple web sites running on a single server, via name-based or IP-based virtual hosts.

https://httpd.apache.org/docs/2.4/vhosts/examples.html

Running several name-based web sites on a single IP address.
Your server has multiple hostnames that resolve to a single address, and you want to respond differently for www.example.com and www.example.org.

Note Creating virtual host configurations on your Apache server does not magically cause DNS entries to be created for those host names. You must have the names in DNS, resolving to your IP address, or nobody else will be able to see your web site. You can put entries in your hosts file for local testing, but that will work only from the machine with those hosts entries.


Using _default_ vhosts  _default_ vhosts for all ports
Catching every request to any unspecified IP address and port, i.e., an address/port combination that is not used for any other virtual host.

<VirtualHost _default_:*>
    DocumentRoot "/www/default"
</VirtualHost>

Using such a default vhost with a wildcard port effectively prevents any request going to the main server.

A default vhost never serves a request that was sent to an address/port that is used for name-based vhosts. If the request contained an unknown or no Host: header it is always served from the primary name-based vhost (the vhost for that address/port appearing first in the configuration file). You can use AliasMatch or RewriteRule to rewrite any request to a single information page (or script).

 


 conclusio - i think that i have to rewrite this directive: 

 

.....so - as far as i unserstand all this have to rewrite the directive to

.*. or to to *

Share this post


Link to post
Share on other sites
  • 0
DaveLegg    1,014

You'd want <VirtualHost *:80> or if you're using SSL, <VirtualHost *:443>

The bit before the : is the IP address, * means to listen on any IP address bound to the server. After the colon, you want port 80 for HTTP or 443 for HTTPS - these are the standard ports used for those services.

Share this post


Link to post
Share on other sites
  • 0
tarifa    0
On 1/27/2020 at 7:58 AM, DaveLegg said:

 

You'd want <VirtualHost *:80> or if you're using SSL, <VirtualHost *:443>

The bit before the : is the IP address, * means to listen on any IP address bound to the server. After the colon, you want port 80 for HTTP or 443 for HTTPS - these are the standard ports used for those services.

 

hello dear Dave - many many thanks for the reply great to hear from you 

finally  fixed it - 

 

needed to create a zone in the primary-nameserver.  Glad that you have helped me with sharing ideas tipps and insights#

 

i am so glad to be part of this great forum 

 

keep up the superb work here. 

 

best regards 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.