[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] catchall for (sub) domain on a RAQ4
- Subject: [cobalt-users] catchall for (sub) domain on a RAQ4
- From: "Martin" <mbruinsm@xxxxxxxxxx>
- Date: Thu Jun 6 02:03:01 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
> > Also, for example, trying sdghfhsdg.domain.com gives a DNS error, and
> > sdgfsdg.anotherdomain.com forwards to the first virtual host defined for
> > that IP (because of the order in the httpd.conf file). Does anybody know
the
> > reason for this strange behavior?
>
> How have you addressed the issue in DNS?
>
> Have you created A or CNAME records for sdgfsdg.domain.com and for
> sdgfsdg.anotherdomain.com? or are you using wildcards in DNS as well.
>
> Thare are real problems with wildcards in DNS... Best carefully read
> the information on wildcards in DNS in the "DNS and Bind" book (the
> "cricket" book) from O'Reilly.
Well, now that you mention it, domain.com uses a different DNS server (that
is, NOT the DNS server on the Cobalt RAQ itself) than anotherdomain.com.
For domain.com, I use *.domain.com in the DNS (A-record) to forward to the
Cobalt RAQ ip. This works just fine, but from then on it messes up, because
instead of forwarding to the virtual host for domain.com, it forwards to the
first virtual host for that ip in the httpd.conf file list. I think this has
to do with Apache (and its ServerAlias directive) not knowing what to do
with the request for domain.com. I did, like I mentioned before, manually
add *.domain.com to the virtual host entry for domain.com, but without
success. Any idea why?
As for anotherdomain.com, it uses the DNS server on the Cobalt RAQ itself.
However, adding an A-record *.anotherdomain.com like somebody suggested,
does NOT work for me, because the cobalt administration does not let me
enter a '*' in the Host Name input field. Does anybody have a solution to
this problem? (maybe adding it manually?)
Thanks,
Marti,