Google Experiences a Glimpse of the NEW .NET DNS
The centralized-net, main-frame-mentality google
watchers have recently experienced a **glimpse**
of the NEW .NET DNS.
DNS is now more and more being handled at the
EDGES of the .NET, not by some out-dated
VAX running BIND in the core.
The main-framers are of course holding on to all
of their old-school out-dated bibles and RFCs
and quoting nonsense as they attempt to explain
what is happening. They can not explain it, they
are out-of-touch, they still believe that
end-users get their DNS from the ICANN root.
The main-framers do not understand dynamic DNS
and edge solutions. They can not imagine that
end-users have **smart DNS resolvers** that work
hard to find something when asked. If google.com
goes away, then google.com.net can step in.
google-com.net can also come into play. ICANN
likes that one because they now want to sell
a lot of .NET names. ICANN has Verisign doing
the Registry out-sourcing at the moment for .NET.
Microsoft, an edge-system supplier, has yet to
play their hand in the NEW .NET DNS era. Stay
Cisco/Linksys has played some of their hand
with the .LAN TLD in the WRT-54G/S WIFI routers.
Did ICANN or the IETF.ISOC say anything ? Of
course not, Cisco is part of their IAB club.
Google has yet to realize that the edge solutions
not only pick off google and head other directions
they also can now front-end Google and hide
google from the end-users. The Google data base
can be mined and then re-worked for the end-user.
The .COM and .NET name-spaces can also be mined
and re-worked for the end-user's consumer root.
DNS is moving to the edges along with end-user
*services*. The centralized-mainframe VAX
programmers still do not get it.
Head on over to the NANOG mail-list to watch
the blind leading the blind, or is that the
BIND leading the BIND ?