-   Linux - Newbie (
-   -   Apache 2.2 setup on Debian, question about name servers (

lppatmore 01-05-2011 09:24 PM

Apache 2.2 setup on Debian, question about name servers
1 Attachment(s)

I'm setting up my Debain machine to host my homepage, and I have installed Apache 2.2, and a browser-based GUI for it called Webmin. I have a domain name with, it is On the domain name site, there are two fields for name servers. Presently, they are set to the name servers for my hosting company.

Apache is working on my machine. When I type my host name in my browser, it goes to index.html in the document root, as it should. When I key in my Debain machine's IP address on another machine on the same network, it also goes to index.html.

Attached, there is a screenshot of the Virtual Server Details in the Webmin GUI. I think I have the server name set right, but what do I type in the Address field? What do I need to type in for my name servers on the domain name site?

Any assistance would be greatly appreciated.

tizzef 01-07-2011 09:00 AM

Hi there,

Could you show us the content of the files in /etc/apache2/site-available/.


lppatmore 01-08-2011 11:24 AM

/etc/apache2/sites-available only contains one file: default-ssl. Should it contain more than one file if I have a virtual host set up in the GUI? Here are the contents:


<IfModule mod_ssl.c>
<VirtualHost _default_:443>
        ServerAdmin webmaster@localhost

        DocumentRoot /var/www
        <Directory />
                Options FollowSymLinks
                AllowOverride None
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all

        ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
        <Directory "/usr/lib/cgi-bin">
                AllowOverride None
                Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
                Order allow,deny
                Allow from all

        ErrorLog ${APACHE_LOG_DIR}/error.log

        # Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn

        CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined

        Alias /doc/ "/usr/share/doc/"
        <Directory "/usr/share/doc/">
                Options Indexes MultiViews FollowSymLinks
                AllowOverride None
                Order deny,allow
                Deny from all
                Allow from ::1/128

        #  SSL Engine Switch:
        #  Enable/Disable SSL for this virtual host.
        SSLEngine on

        #  A self-signed (snakeoil) certificate can be created by installing
        #  the ssl-cert package. See
        #  /usr/share/doc/apache2.2-common/README.Debian.gz for more info.
        #  If both key and certificate are stored in the same file, only the
        #  SSLCertificateFile directive is needed.
        SSLCertificateFile    /etc/ssl/certs/ssl-cert-snakeoil.pem
        SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key

        #  Server Certificate Chain:
        #  Point SSLCertificateChainFile at a file containing the
        #  concatenation of PEM encoded CA certificates which form the
        #  certificate chain for the server certificate. Alternatively
        #  the referenced file can be the same as SSLCertificateFile
        #  when the CA certificates are directly appended to the server
        #  certificate for convinience.
        #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt

        #  Certificate Authority (CA):
        #  Set the CA certificate verification path where to find CA
        #  certificates for client authentication or alternatively one
        #  huge file containing all of them (file must be PEM encoded)
        #  Note: Inside SSLCACertificatePath you need hash symlinks
        #        to point to the certificate files. Use the provided
        #        Makefile to update the hash symlinks after changes.
        #SSLCACertificatePath /etc/ssl/certs/
        #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

        #  Certificate Revocation Lists (CRL):
        #  Set the CA revocation path where to find CA CRLs for client
        #  authentication or alternatively one huge file containing all
        #  of them (file must be PEM encoded)
        #  Note: Inside SSLCARevocationPath you need hash symlinks
        #        to point to the certificate files. Use the provided
        #        Makefile to update the hash symlinks after changes.
        #SSLCARevocationPath /etc/apache2/ssl.crl/
        #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

        #  Client Authentication (Type):
        #  Client certificate verification type and depth.  Types are
        #  none, optional, require and optional_no_ca.  Depth is a
        #  number which specifies how deeply to verify the certificate
        #  issuer chain before deciding the certificate is not valid.
        #SSLVerifyClient require
        #SSLVerifyDepth  10

        #  Access Control:
        #  With SSLRequire you can do per-directory access control based
        #  on arbitrary complex boolean expressions containing server
        #  variable checks and other lookup directives.  The syntax is a
        #  mixture between C and Perl.  See the mod_ssl documentation
        #  for more details.
        #<Location />
        #SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
        #            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
        #            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
        #            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
        #            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20      ) \
        #          or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/

        #  SSL Engine Options:
        #  Set various options for the SSL engine.
        #  o FakeBasicAuth:
        #    Translate the client X.509 into a Basic Authorisation.  This means that
        #    the standard Auth/DBMAuth methods can be used for access control.  The
        #    user name is the `one line' version of the client's X.509 certificate.
        #    Note that no password is obtained from the user. Every entry in the user
        #    file needs this password: `xxj31ZMTZzkVA'.
        #  o ExportCertData:
        #    This exports two additional environment variables: SSL_CLIENT_CERT and
        #    SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
        #    server (always existing) and the client (only existing when client
        #    authentication is used). This can be used to import the certificates
        #    into CGI scripts.
        #  o StdEnvVars:
        #    This exports the standard SSL/TLS related `SSL_*' environment variables.
        #    Per default this exportation is switched off for performance reasons,
        #    because the extraction step is an expensive operation and is usually
        #    useless for serving static content. So one usually enables the
        #    exportation for CGI and SSI requests only.
        #  o StrictRequire:
        #    This denies access when "SSLRequireSSL" or "SSLRequire" applied even
        #    under a "Satisfy any" situation, i.e. when it applies access is denied
        #    and no other module can change it.
        #  o OptRenegotiate:
        #    This enables optimized SSL connection renegotiation handling when SSL
        #    directives are used in per-directory context.
        #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
        <FilesMatch "\.(cgi|shtml|phtml|php)$">
                SSLOptions +StdEnvVars
        <Directory /usr/lib/cgi-bin>
                SSLOptions +StdEnvVars

        #  SSL Protocol Adjustments:
        #  The safe and default but still SSL/TLS standard compliant shutdown
        #  approach is that mod_ssl sends the close notify alert but doesn't wait for
        #  the close notify alert from client. When you need a different shutdown
        #  approach you can use one of the following variables:
        #  o ssl-unclean-shutdown:
        #    This forces an unclean shutdown when the connection is closed, i.e. no
        #    SSL close notify alert is send or allowed to received.  This violates
        #    the SSL/TLS standard but is needed for some brain-dead browsers. Use
        #    this when you receive I/O errors because of the standard approach where
        #    mod_ssl sends the close notify alert.
        #  o ssl-accurate-shutdown:
        #    This forces an accurate shutdown when the connection is closed, i.e. a
        #    SSL close notify alert is send and mod_ssl waits for the close notify
        #    alert of the client. This is 100% SSL/TLS standard compliant, but in
        #    practice often causes hanging connections with brain-dead browsers. Use
        #    this only for browsers where you know that their SSL implementation
        #    works correctly.
        #  Notice: Most problems of broken clients are also related to the HTTP
        #  keep-alive facility, so you usually additionally want to disable
        #  keep-alive for those clients, too. Use variable "nokeepalive" for this.
        #  Similarly, one has to force some clients to use HTTP/1.0 to workaround
        #  their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
        #  "force-response-1.0" for this.
        BrowserMatch "MSIE [2-6]" \
                nokeepalive ssl-unclean-shutdown \
                downgrade-1.0 force-response-1.0
        # MSIE 7 and newer should be able to use keepalive
        BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown


120 01-08-2011 11:49 AM


Normally on Apache2 with Debian, Virtual Hosts are created in /etc/apache/sites-available and the tool 'a2ensite <vhost>' does the donkey work of adding links into /etc/apache/sites-enabled. From their a reload of Apache will allow your Virtual Host to work. This keeps things tidy, separate and easy to manage.

That said, it's not the only way to add a virtual host. It's not uncommon to find them in httpd.conf or even on the end of /etc/apache2/apache2.conf in Debian. Webmin may just do this - but I don't know. It's worth checking.

To test the virtual host you can't just call the IP of the server, because that calls the default site. The host header needs to be set to the name of your virtual host. Probably the easy way to do this (for testing) is to add an entry to your hosts file pointing: to the IP of the server. Then, when you call the site from your favorite browser the host header should be correct. Naturally, other hosts you want to test this with (lin or win) will need to have this entry in their hosts file until you set it in stone (dns). Don't forget to remove the host entries when done testing.

For the outside world to reach it, you'd just set your DNS to resolve to the IP of your server.(Personally I would also map it without the www too).

Hope that helps.

Reverend Majestic Scamaster
419 Christian Church of the Debian

All times are GMT -5. The time now is 01:19 PM.