On Mar 1, 2015, at 8:07 AM, Florian Weimer <[email protected]> wrote: >> On Mar 1, 2015, at 2:47 AM, Florian Weimer <[email protected]> wrote: >>> The final part is the problem. Name resolution has to include other >>> information source besides DNS, and it's difficult to merge this data >>> with your own DNS resolver (whether you wrote it yourself, or it's >>> some library you got from somewhere). >> >> Difficult, but not impossible. The getdns API included non-DNS >> information from the beginning, and Verisign is working on getting >> that part into their implementation. > > The API design isn't the real issue here, it is interacting with the > Name Service Switch in a way that is compatible with all existing NSS > modules.
Yep, that's part of the implementation, and Verisign seems quite aware of it. Note, too, that Microsoft is free (even encouraged!) to adopt the getdns API and implement it themselves. --Paul Hoffman _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
