Date: Fri, 27 Apr 2001 13:39:26 +1000 From: Tony Landells <ahl@austclear.com.au> To: "Jonathan Fortin" <jfortin@akalink.com> Cc: questions@freebsd.org Subject: Re: *.example.net Message-ID: <200104270339.NAA26008@tungsten.austclear.com.au> In-Reply-To: Message from "Jonathan Fortin" <jfortin@akalink.com> of "Thu, 26 Apr 2001 23:33:08 -0400." <000d01c0ceca$c7856e20$0200320a@node00>
next in thread | previous in thread | raw e-mail | index | archive | help
jfortin@akalink.com said: > The whole point of using wildcard DNS in my regard is if you got a > production website, you would point *.yourdomain.com to the IP address > to redirect impotent users to your homepage, then you can rewrite the > HTTP_HOST header with mod _rewrite making it seem like they didn't > mistype it which is actually good, but either then that I wouldnt see > the use. That's an interesting idea, but I'd submit that if you've followed convention and named your Web site "www.yourdomain.com", then the only thing you're saving them from is mistyping "www", because if they mistype "yourdomain.com" they're not going to get your DNS server anyway. If you haven't followed convention then you're making life difficult for other people anyway, and making "all roads lead to Rome" would seem a contradiction. If you had a good reason for not naming your Web server "www" but want people to find it as "www", then you can put in a separate A record or CNAME record that leads them in the right direction. Cheers, Tony -- Tony Landells <ahl@austclear.com.au> Senior Network Engineer Ph: +61 3 9677 9319 Australian Clearing Services Pty Ltd Fax: +61 3 9677 9355 Level 4, Rialto North Tower 525 Collins Street Melbourne VIC 3000 Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104270339.NAA26008>