Re: enough is enough

> On 21 dec 2014, at 10:44, bert hubert <[email protected]> wrote:
> 
> On Sun, Dec 21, 2014 at 06:34:02AM +0100, Patrik Fältström wrote:
>> - ...policy in some registries require NS records for registrations of a domain (i.e. no difference between registration and delegation), there will be lame delegations
> 
> To clarify, nothing like this is what I intended. Perhaps a prototype will
> help:
> 
> "Dear domain operator, nameserver vendor, or load balancer purveyor,
> 
> The domain x.y.z fails to resolve using our software, and we have determined
> that this is because the software or hardware publishing the DNS details of
> x.y.z is not conforming to the DNS standards.
:
:

As Jim says, your idea is nice as it is, and there is nothing wrong with the email -- but we have no idea what so ever where to send it.

The best path forward is I think still for you to publish clear and crisp information like this on your web page so that it is found when searching for help with Google and other search engines.

I.e. as long as no one have any issues with the brokenness, it will not be fixed.

And obviously it is not broken enough. The parties involved (the one looking things up and the domain name holder) obviously either can communicate anyways with the brokenness or they do not find lack of communication is bad enough to fix whatever is to be fixed.

I feel very sad to have this view today, because I did not have it earlier. I have though given up on the mass market operational community and feel one have to spend time where it actually matters, on software, best practices etc.

If not even TLDs are hosted correctly, and registry policies are such that it encourages broken DNS configurations, I feel there is not much The Protocol Police can do about it.

   Patrik

_______________________________________________
dnsext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsext

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFUlqHurMabGguI180RAolyAJsHji3c+fZSgZkICEpUchKUsCJeLQCfRTgB
NYYtkXdmyzea/up5ZzdzyNk=
=lxPN
-----END PGP SIGNATURE-----