Re: [cobalt-developers] Sub-domain Question (please help)

["Michael" <michael@xxxxxxxxxxxxxxx>]

I know you are very reluctant to give me this information, but I am still
confused as to what I would need to do.  Maybe you could answer some of my
questions below:

1.  If I were to enable DNS wildcards on a domain, would the wildcards be
enabled on all the domains or just the one that I wanted to enable it for?

2.  When DNS wildcards are enabled on a domain then you cannot add
sub-domains (sub.yourname.com) using the regular cobalt administration,
right?  (Is this what you were explaining below because I was a little
confused)

3.  Shouldn't there be an easy way to redirect all sub-domains of a domain
name to the corresponding sub-directory?  For example...  test.yourname.com
forwards to yourname.com/test.  Kind of like a default thing in the DNS
configurations...  I don't know...

4.  What exactly would I need to do to enable wildcards on my raq3 if I
decide that your answers to questions 1 and 2 are to my liking?

Thanks!
Michael


----- Original Message -----
From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
To: <cobalt-developers@xxxxxxxxxxxxxxx>
Sent: Wednesday, May 17, 2000 1:09 AM
Subject: Re: [cobalt-developers] Sub-domain Question (please help)


> Okay, I suppose I'm going to have to answer this, as much as I don't
> like wildcard DNS and as sure as I am that it will eventually bite
> you...
>
> "DNS and Bind", the O'Reilly book only describes the use of wildcards in
> MX records, but they will work in other record types as well.
>
> So you could have a record like this:
>
> *   IN   A   192.253.253.113
>
> but the problem is that this will ONLY work for domains for which there
> are NO other records in the DNS.
>
> For example, if you then have a record such as:
>
> manny  IN  NS  ns1.yourdomain.com
>
> and another such as:
>
> moe    IN  MX  mail.yourdomain.com
>
> and another such as;
>
> jack   IN  ns  ns1.yourdomain.com
>
> then john.yourdomain.com will resolve to 192.253.253.113, but
> manny.yourdomain.com, moe.yourdomain.com, and jack.yourdomain.com won't
> resolve.
>
> Sure you can keep track of this when you first create the records, but
> how about over the years as your DNS grows?
>
> Also, according to DNS and Bind, page 378, "The danger with wildcards is
> that they clash with search lists."
>
> Read the appropriate sections of DNS and Bind.  If you understand them
> perfectly and know you still need to use wildcards, then use them.
> Beware.
>
> (And I have no idea if they work within the constrains of the gui or
> not, since I've never tried them there.)
>
> And once you've used them, then how do you "move" the request to a
> subdirectory?  Do you already have a copy of info.cgi?  Have fun <wry
> grin>.
>
> BTW, I like to do what you're doing, too.  It's easy on a non-Cobalt-RaQ
> generic linux system; you just create a virtual domain for
> "manny.yourname.com" and make the default directory
> "yourname.com/manny".  Works fine, but not with the RaQ gui.
>
> Jeff
>
> Michael wrote:
>
> > Hello,
> >
> > We would like to offer something on our server that will forward a
> > sub-domain *.yourname.com to a sub-directory yourname.com/*.  Is there
> > anyway that this can be done?
> >
> > An example of this is available here:
> >
> >
http://www.domaindirect.com/cgi-bin/info.cgi?salesid=&do=sub-domain&ref=DDos
> > rs00.
> >
> > I've been told that DNS wildcards can be enabled and then you can use a
> > script to get this to work.  If that is the case, and the only way of
doing
> > this, then how would I enable wildcards on *.yourname.com?
> --
> Jeff Lasman <jblists@xxxxxxxxxxxxx>
> nobaloney.net
> P. O. Box 52672
> Riverside, CA  92517
> voice: (909) 787-8589  *  fax: (909) 782-0205
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>