> For example, assume that our two server names are
> Both are duly registered with internic. Both have CNAME records
> pointing to a machine at 143.43.290.45
> We would like a net surfer coming in
> to get a different home page than someone coming in as
> We don't want to force them to type a different port number when they
> enter the URL in their browser. We don't want a different home page name.
The use of CNAME records vs. multiple A records is being discussed openly
on comp.protocols.tcp-ip.domains as I write this. Some are advocating the
use of multiple CNAME records in most cases, others multiple IP addresses
with matching multiple PTR records for the in-addr.arpa registrations.
Suffice it to say that I think you can get something that will work for
what you're trying to do either way.
However, if you use TCP-Wrappers to listen to the WWW port, and then based
on the domain name specified by the remote end, fire up a different WWW
server, that would probably be done most easily with multiple A records
instead of the CNAME records -- I don't know if the name would get
canonicalized out before the query got to your end or not.
If you're interested in exploring TCP-Wrappers in this fashion, I recommend
you fire up your local archie client and search for "tcp-wrappers" or
"tcp_wrappers". I think an old version may be found somewhere on
ftp.uu.net, but I can't recall where. Last I heard, the most recent
version was 7.2, which I don't think is found too many places outside the
official anonymous ftp site for it that Wietse Venema (I think I spelled
that right) has set up. I've pulled 7.2 for use on our machines at work,
and it appears that the improvements over 7.1 and 7.0 are fairly minor and
mostly cosmetic, but as far as I'm concerned, it's best to start with the
most recent version and not futz around with the older versions and end up
possibly needing to upgrade anyway.
The comp.mail.sendmail FAQ is located at:
Want to know about the latest version of BIND? Check out: