Resolving external domain names with NCSA

Resolving external domain names with NCSA

Post by Ralph Maye » Sat, 30 Mar 1996 04:00:00



We are running the NCSA server on Sun, and recently took a stab
at generating statics on use with the wwwstat package from
University of California, Irvine.  The page counts are great,
but all the client domain references are unresolved.  How do we
get these resolved?  Is this something we do in the server so
that it is in the log, or should it be done by a postprecessor
of some sort?

Many thanks for any help.

Ralph Mayer
Adra Systems Inc
http://www.adra.com

 
 
 

Resolving external domain names with NCSA

Post by Mark Schmit » Tue, 02 Apr 1996 04:00:00



>We are running the NCSA server on Sun, and recently took a stab
>at generating statics on use with the wwwstat package from
>University of California, Irvine.  The page counts are great,
>but all the client domain references are unresolved.  How do we
>get these resolved?  Is this something we do in the server so
>that it is in the log, or should it be done by a postprecessor
>of some sort?

We use the wwwstat package as well. It has well structured output that can
be fed to gwstat for some nice looking graphs. In NCSA version 1.5 there is
a log option in the httpd.conf file. We use the following which is pretty
close to the log format that the old virtual server patches for 1.4 used.

LogOptions Separate Servername Date
                    ^^^^^^^^^^
The "Servername" part is what you are looking for I think. The domain name
that was serving the request just got moved to the end of the log record, so
a little hacking on wwwstat was necessary to allow it to find the name. I
just
added another switch to allow a wwwstat run for each domain name that wanted
a report. If your server isn't too loaded and the log files don't get too
large, you will be fine. However if your logs get too big like ours did you
will want to separate at least the transfer or access logs into one per
domain
scheme which you can do inside the <VirtualHost> directive like the
following:

<VirtualHost www.mydomain.com>
    ServerName www.mydomain.com

    TransferLog /Public/mydomain/stats/access_log
    <SRMOptions>
        DocumentRoot /Public/mydomain
    </SRMOptions>
</VirtualHost>

Dealing with large numbers of virtual servers is another story altogther,
and is being discussed in a couple of other threads in this newsgroup.

I hope this helps...

Regards,
Mark
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Engineering International, Inc.                       Voice:    (505)343-1060

         Rt66.com - Dial-up Public Internet Access in New Mexico
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 
 
 

1. resolve.conf (domain name resolving on client)

Just upgraded from Solaris 8 to 9.  Some of the simple things are
stumping me at the moment.

I am simply trying to get my workstation to have domain names
resolved.  I can toss an ip address into my browser URL, but not a
domain name.  I have added two nameserver entries into my
/etc/resolv.conf, but they evidently are not being read.  I know that
would do the trick with Linux.

I guess there is something else with Solaris?  Nearly all the usenet
posts and such I can find relate to setting up DNS servers....don't
need that.

Can anyone help?  Thanks!
Rob

2. Modem Setup

3. Resolving domain.com as well as name.domain.com

4. NFS fs read-only when mounted read-write

5. named and static IP to resolve domain name

6. Yet Another X Hardware Problem ADI 4V

7. insmod external names resolving problem

8. xf86config with tnt2 and intellimouse

9. BIND doesn't resolve my domain name

10. DNS - nonexistant names are resolved to my domain

11. resolving domain names

12. I can't resolve domain names using my ISP DNS Server!!!!

13. Resolve domain name w/o DNS?