[RFCI-Discuss] Change to bogusmx policy

[Simon Arlott]

On 04/07/08 15:14, Derek J. Balling wrote:
> This is a minor change, and should not affect that many people, but it
> triggered a bug in the checker this morning, so I fixed by bug by adding
> a listing criteria. :-)
> 
>> Domains which have bad glue records (e.g., the root servers point to
>> ns5.example.com but the example.com NS set does not list an
>> ns5.example.com) are considered listable, as this sort of situation
>> can lead to undeliverable mail.
> 
> In the current "test-case", it returns as such:
> 
> Looking up "f1computersolutions.com":
> 
>> Current status:
>> Return Code: 11
>> Description: j.gtld-servers.net points to ns5.f1networks.net as
>> authoritative, but ns5.f1networks.net doesn't exist.
> 
> 
> As always, I'm willing to discuss if someone thinks this is a "bad
> decision". The way this was implemented in the code would be easy to
> have this case "fail good" if we wanted to, but I'm not sure why we would.

Unfortunately this is legitimate, the domain has been delegated to those 
servers and they are authoritative for it. If they want to present different 
NS than the root gave then that's ok.

The root has glue for ns5.f1networks.net which can be used to connect to 
it (and it does respond). So the glue's not bad either.

There could still be an RFC against this sort of thing...

-- 
Simon Arlott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3619 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.megacity.org/pipermail/rfci-discuss/attachments/20080704/5404891c/attachment.bin