News for hackers. Stuff that matters.
Re:The .blog Bait and Switch by hueving on Thursday November 17, 2016 @02:02PM (#12980336)
The DNS resolver is configurable, not hard coded. Forcing a switch would require OS vendors to ignore the resolver issued via DHCP, which would not work on many corporate networks that block outbound DNS not via their resolver.
Re:The .blog Bait and Switch by bagosm on Thursday November 17, 2016 @04:05PM (#12981561)
Maybe then just prefer if reachable? Soon enough it's the new standard.
Re:The .blog Bait and Switch by ygaels_armpit on Thursday November 17, 2016 @04:12PM (#12981628)
Yes I think any new system would have to see the old one grandfathered (give the current incumbents time to find something useful to do instead of jetting off to conferences all year).

Browsers/OS would be reasonably easy in most circumstances, but there are embedded devices, load-balancing configurations, other esoteric uses for DNS (text records, mail etc) that'd have to be considered as well.

Re:The .blog Bait and Switch by Senji on Friday November 18, 2016 @10:54AM (#12987581)
An attack surface is ISPs and Governments strongarming them to use their own DNS roots which can then be plugged into the "new" root servers conforming with the theoretical browser vendor, os vendor alliance.
Re:The .blog Bait and Switch by __jal on Thursday November 17, 2016 @05:54PM (#12982528)
Pick your favorite:

https://en.wikipedia.org/wiki/Alternative_DNS_root

There are others. But no, they don't become the new standard.