RE: [OT] Re: Vhosts + mod_perl

2001-12-03 Thread Jonathan M. Hollin

:: Everytime I make a new document root for a different website, say the
:: subdomain loco on trains.ath.cx, do I need to update the DNS?
::
:: For foo.trains.ath.cx and bar.trains.ath.cx do I need to make new DNS
:: entries for foo and bar subdomains? Surely I don't? Because browsers
:: will ask for it, and get directed to trains.ath.cx, and my apache will
:: take are of the rest from the HTTP 1.1 Host: field?

If you are adding sub-domains then, of course, you need to update your DNS.
Without a corresponding DNS entry, how could foo.trains.ath.cx ever be
resolved?

Jonathan M. Hollin - WYPUG Co-ordinator
West Yorkshire Perl User Group
http://wypug.pm.org/




Re: [OT] Re: Vhosts + mod_perl

2001-12-03 Thread Dave Baker


--82I3+IH0IqGh5yIs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Dec 02, 2001 at 04:19:28PM -, Jonathan M. Hollin wrote:
 :: Everytime I make a new document root for a different website, say the
 :: subdomain loco on trains.ath.cx, do I need to update the DNS?
 ::
 :: For foo.trains.ath.cx and bar.trains.ath.cx do I need to make new DNS
 :: entries for foo and bar subdomains? Surely I don't? Because browsers
 :: will ask for it, and get directed to trains.ath.cx, and my apache will
 :: take are of the rest from the HTTP 1.1 Host: field?
=20
 If you are adding sub-domains then, of course, you need to update your DN=
S.
 Without a corresponding DNS entry, how could foo.trains.ath.cx ever be
 resolved?


Actually, it's possible to create a wildcard domain so that
*.trains.ath.cx will resolve identically. =20

If you choose to do this you no longer have to update DNS for new hosts
but run the risk of people getting inappropriate errors when using a
hostname that shouldn't exist.  Instead of getting 'no such host' they'll
end up with a valid IP and will hit your web server which then has to
decide how to handle it.

As an example, your zone file can look just as follows - I've split www
and vhosts onto separate IP addresses but this isn't required, as you can
mix named and wildcard entries fairly freely.  If you use tools such as
dnslint you may need to append a comment on the end of your wildcard line
to indicate to dnslint that the wildcard is intentional.

(header fluff)

;; 'real' host
www   IN  A   123.123.123.1
vhost IN  A   123.123.123.2

ftp   CNAME   www.trains.ath.cx.

;; everything else.
* CNAME   vhost.trains.ath.cx.

(footer fluff)


Dave

--=20

- Dave Baker  :  [EMAIL PROTECTED]  :  [EMAIL PROTECTED]  :  http://dsb3.com/ -
GnuPG:  1024D/D7BCA55D / 09CD D148 57DE 711E 6708  B772 0DD4 51D5 D7BC A55D


--82I3+IH0IqGh5yIs
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8C5mSDdRR1de8pV0RAuEdAJ0bbe0lT0ydp1dVyMNLOKhTLYiK3QCgtEdx
IJx5OkyMuKKWDjOYq4UMKiM=
=DBLt
-END PGP SIGNATURE-

--82I3+IH0IqGh5yIs--