[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] redirect
- Subject: Re: [cobalt-users] redirect
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Wed Apr 24 21:08:08 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
JL> Date: Wed, 24 Apr 2002 20:19:25 -0700
JL> From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
JL> Never is a long time Maurice. You should never use a CNAME to point to
JL> either the domain or the hostname.domain on any RaQ that's also going to
JL> be pointed to by a mail-server, but that's about the only limitation.
Don't have CNAMEs point to CNAMEs, either.
JL> Using a CNAME is a quick and simple solution, and frankly, I like to
Actually, I used to use CNAMEs more than I do now. Multiple A
records pointing to one IP is "officially" a bad idea, but I now
prefer that over the multiple queries required with CNAMEs.
Besides, anything that a CNAME can do, "sed" can too -- unless a
CNAME points to a host for which I don't do DNS. (I definitely
tend to run CNAMEs in this case.)
JL> think elegant. But it won't work unless the target URL has it's own
JL> dedicated IP#.
Uhhhhh.....
DNS converts FQHN to IP. Web browser contacts webserver on that
IP, and sends request using "Host: " field in header. Apache
"ServerName" directive matches host.
--
Eddy
Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.