[ On Thursday, March 29, 2001 at 16:08:56 (-0500), Dave C. wrote: ]
> Subject: Re: [Exim] Slightly OT DNS<->MTA problem
>
> is not allowed. That doesnt mean people dont do it, but its against the
> relevant DNS RFC's and will cause problems like you have described.
People do it only because they still run broken nameservers that allow
them to do it. Hopefully they'll all be hacked soon (and thus upgraded).
> The thing to do is inform your customer that their website is
> "www.customer.com", and not "customer.com", becuase website hostnames
> have to have an actual host name and not just a domain. If their ad
> people put "customer.com" in their billboards/etc, then that is a
> mistake on the ad people.
Why? It's perfectly A-OK to have an A record at the same level as the
SOA and thus for "
http://customer.com/" work. Same thing for MX records
at the SOA level so that <foo@???> works too.
Note that you really should have an MX for the mail host itself, so even
if the same host services SMTP as you've listed at your SOA level, you
should still have an MX pointing to itself, eg.:
@ IN SOA customer.com. postmaster.customer.com. (...)
IN NS customer.com.
IN NS ns.isp.net.
IN MX 0 customer.com.
IN A 192.168.1.1
(note here the same host is also the nameserver....)
--
Greg A. Woods
+1 416 218-0098 VE3TCP <gwoods@???> <robohack!woods>
Planix, Inc. <woods@???>; Secrets of the Weird <woods@???>
