Date: Fri, 27 Apr 2001 13:26:22 +1000 From: Tony Landells <ahl@austclear.com.au> To: "Christopher Leigh" <clcont@gmx.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: *.example.net Message-ID: <200104270326.NAA25642@tungsten.austclear.com.au> In-Reply-To: Message from "Christopher Leigh" <clcont@gmx.net> of "Fri, 26 Oct 2001 22:16:26 EST." <000b01c15e95$c4bb6cc0$0101a8c0@contrec>
next in thread | previous in thread | raw e-mail | index | archive | help
I've never heard of anyone doing wildcard A records... Back in the days when people weren't very good at hiding hostnames in email they used to use wildcard MX records. They were generally considered a necessary evil, but people who had the skill were advised to hide the hostnames in email instead and abolish the wildcard MX. The reason I mention this is that the fundamental thing is the same-- you're trying to solve a problem that shouldn't exist. The whole point of DNS is to tell you the address for valid servers. If you return an address for any hostname in your domain, then people who have mis-typed a hostname will then have to wait for their data (HTTP, SMTP, telnet, whatever) connection to time out, rather than coming back immediately and telling them the hostname is wrong. Mind you, I can see some applications for this, but the majority of the advantages are spurious at best. And since the only place you should be advertising an RFC 1918 address like 192.168.1.1 is on your internal network, all you're going to do is annoy your users. 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?200104270326.NAA25642>