Hi Paul, On 09/14/2014 10:37 AM, Paul wrote: > That would be hard. Aren't all godaddy hosted domains (not godaddy itself) > broken? That's why we had to disable this feature in fedora/RHEL
Fortunately Godaddy hosted domains were fixed for some times now. Here, I re-enabled use-caps-for-id since 2013/07/22 and didn't have any issue since then. Regards, Simon > Sent from my iPhone > >> On Sep 14, 2014, at 1:52, Rygl Aleš <[email protected]> wrote: >> >> Dear all, >> >> We use use-caps-for-id for about 5 millions of customers without >> problems on our resolvers for about a year. During this time I had to solve >> just several issues of unresolvable domains because of wrong implementation >> of >> 0x20 draft. The biggest issue we had with ustream.tv but they fixed it >> within >> couple of days. The worst thing here seems to be finding a way how report >> the >> issue and contact people responsible for authoritative DNS servers without >> registering to different services with emails and personal details (I am >> having >> 0x20 issue with alibaba.com now and their email in SOA does not work). >> We have quite large setup (eight resolvers, 70 Gigs cache) and I would not >> like to switch 0x20 support off just because of several sites per year. >> >> So I would like to ask you if it would be possible to implement some kind of >> unboun-control manageable list for domains that are not working correctly. >> The >> result of validation of 0x20 would be ignored for them. >> >> Thanks >> Regards >> >> Ales >> >> >> _______________________________________________ >> Unbound-users mailing list >> [email protected] >> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users > _______________________________________________ > Unbound-users mailing list > [email protected] > http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users > _______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
