| I haven't found it yet. I'm pretty sure the discussion against it was in
| O'Reilly's "TCP/IP Network Administration". I've browsed through it in my
I've got that one and their DNS/BIND book at home - I'll glance through them
tonight.
| I had this problem at a place I consult for. They adv
This goes back to the original discussion about why the mails where
being directed to the domain A record, but at the ISP's request we have
put dummy MX records of mail. in the zones and then assigned
those hosts the ip of 127.0.0.1, appears to be working quite well the
spammers can send mail to t
First, there's no DNS RFC (yes, I've read them) that states that
putting an A record on a domain.tld is wrong. So, you're most welcome
to do so, if you so desire. However, be warned that doing so as regular
practice is like swimming with piranas. You can do it, but it isn't
necessarily wise.
I haven't found it yet. I'm pretty sure the discussion against it was in
O'Reilly's "TCP/IP Network Administration". I've browsed through it in my
spare time and didn't find it. The worst problem with this is when users
don't know you, say FTP server's address and give domain.tld a whirl. It
m
| IIRC, I recall an arguement that strongly says you aren't supposed to put
| an A on a domain. I forget what the main reasons were though.
I'd be interested in finding out. I typically put an A record on
'domain.tld', then CNAME the 'www' host to it. That way, a person can type
"domain.tld" or
One of the many reasons I never put an A record on a domain name. I had a
hell of a conversion at an ISP I consult with when they moved from a one
server to many server setup. Previously they'd advertised domain.tld for
*everything*; MX, www, POP, SMTP, you name it. Everything was domain.tld.
T
It's a normal behavior. If you do not have a specific MX record for the
domain, the mail servers will look to the A record for the domain. So, if
www.domain.com has the same A record as domain.com, or if domain.com is
CNAME'd to www.domain.com, than that system will receive the mail for
doma
: [SAtalk] SPAM related, but not SPAMASSASSIN question
In the absense of MX records, MTAs try the A record if it exists
(it's a "fake" "MX 0" record). So you probably have an A or CNAME for
"domain.com" to your webserver, which means the mail goes to your ISP
n
On Tue, Oct 08, 2002 at 08:07:11AM -0600, Terry Poperszky wrote:
> I maintain about 20 different domain registrations, only a couple of
> which receive emails (At least legitimate ones). One domain that had
> been receiving emails and was now defunct, was still receiving hundreds
> of SPAM mails p
Title: SPAM related, but not SPAMASSASSIN question
If there is a better list for this, please feel free to direct me to it.
I maintain about 20 different domain registrations, only a couple of which receive emails (At least legitimate ones). One domain that had been receiving emails and was
10 matches
Mail list logo
