> That's probably technically slightly too much (TCP support is just > a SHOULD I think), but in practice it is a good thing to check TCP is required for MX lists which are truncated. RFC 1123, section 6.1.3.2: A mailer must not use a truncated MX response, since this could lead to mail loops. TCP is not required if you can restrict the number and size of MX entries for a domain name beforehand. Otherwise nobody will be able to send mail to the affected domain names, which will invalidate the zone. -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
- Re: Bogus nic.fr behavior Bill Manning
- Re: Bogus nic.fr behavior Randy Bush
- Re: Bogus nic.fr behavior D. J. Bernstein
- Re: Bogus nic.fr behavior M�ns Nilsson
- Re: Bogus nic.fr behavior James Raftery
- Re: Bogus nic.fr behavior M�ns Nilsson
- Re: Bogus nic.fr behavior James Raftery
- Re: Bogus nic.fr behavior Francois romieu
- Re: Bogus nic.fr behavior Mark . Andrews
- Re: Bogus nic.fr behavior Robert Elz
- Re: Bogus nic.fr behavior Eric A. Hall
- Re: Bogus nic.fr behavior Marco d'Itri
- Re: Bogus nic.fr behavior Jerry Scharf
- Re: Bogus nic.fr behavior Robert Elz
- Re: Bogus nic.fr behavior Harald Alvestrand
- Re: Bogus nic.fr behavior Robert Elz
- Re: Bogus nic.fr behavior Jerry Scharf
- Re: Bogus nic.fr behavior D. J. Bernstein
- Re: Bogus nic.fr behavior Matt Crawford
