I am extremely concerned about giving even the slightest [mistaken] impression that anyone's NS are located at IANA [other than a handful of I* community sites of course].
I understand your concerns; if we want to replace example.com IMHO we must find a couple of suitable, short and easy names, maybe also fictional, and use them to label the target domain and its authoritative servers. Can we use something on the ripe.net zone?
Perhaps we could use something like example-network-A.com, example-network-B.com, example-network-C.com as the Name Server host networks.
They could be valid but I'm afraid that they are too long and too similar.
I realise that if users of *some* legacy systems can employ circumvention it's still a problem, but the migration to mobile platforms is rapid and significant, and they are much less susceptible to user customisation.
While providing a mobile-focused overview may be a good idea, I think that we should not suggest governors and lawmakers to positively judge a blocking measure just because it's not easy to circumvent on some devices (and that's not totally true too - please see below). I think we should pursue a globally valid criterion and we must avoid recommendations based only on difficulties that users may encounter to bypass blocking systems. Moreover, most of the issues I can see are not related to the efficacy of blocking measures, but to damage and side effects that they imply.
On my Android phone, for example, I can't even see a way to change it from DHCP (which I assume it's using) to a fixed DNS server of *my* choice. I imagine an iPhone or iPad is the same.
On your wifi network you can change your DHCP server configuration and send them your preferred DNS servers. An app to change DNS on Android and an iPhone guide follow; I can't tell you if they work, but from a quick search on Google it seems that's not so hard to change configurations on mobile devices. Also VPNs are easy to setup on both systems. https://play.google.com/store/apps/details?id=uk.co.mytechie.setDNS http://www.macinstruct.com/node/558 -- Pier Carlo Chiodi http://pierky.com/aboutme The opinions expressed here represent my own and not those of any organization, entity or committee to which I may hold a position.
