Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.protocols.dns.bind > #15954
| From | Matus UHLAR - fantomas <uhlar@fantomas.sk> |
|---|---|
| Newsgroups | comp.protocols.dns.bind |
| Subject | Re: Dumb Question is an A or AAAA record required? |
| Date | 2020-07-09 16:24 +0200 |
| Message-ID | <mailman.677.1594304652.942.bind-users@lists.isc.org> (permalink) |
| References | <B1C7B197-34CE-42AB-92CC-69F65B35D3FD@kreme.com> <7ab19939-3025-c874-e5a4-97721eb435fc@ripe.net> <ep8egf1jv84i97uev69vr17ld66g4fave6@m78> <20200709142438.GA30977@fantomas.sk> |
On 09.07.20 15:06, Matthew Richardson wrote: >On a related issues there were (perhaps long ago) issues if the A record >for a domain had an SMTP server on it, where email could sometimes be >delivered to that A record rather than the MX. I had (again long ago: >10-15 years) actually seen this occur. If there is MX record for a domain, a MTA MUST only use MX record when delivering to that domain. If there is no MX record for a domain, but an A record is available, MTA uses default MX with preference of 0 pointing to that A records. This is how it's defined to work, this is not "an issue about that". >Do people think that this problem could still occur these days? What sort >of transient (presumably DNS) failure might cause an SMTP server to deliver >to A rather than MX? the only DNS failure that could cause this (and I can think of now) is if DNS server incorrectly returned NODATA for MX record (effectively saying there's no MX). -- Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Spam = (S)tupid (P)eople's (A)dvertising (M)ethod
Back to comp.protocols.dns.bind | Previous | Next | Find similar
Re: Dumb Question is an A or AAAA record required? Matus UHLAR - fantomas <uhlar@fantomas.sk> - 2020-07-09 16:24 +0200
csiph-web