Yeah, a lot of providers are, and have been doing this for a while. It's
DNS based, performed w/wild cards, and can be avoided by using DNS
servers other than the one's that you're configured to use via DHCP.
Recommendations - don't use the DNS servers that your ISPs provide for
you via DHCP unless you're using an Inclusive Name Space Friendly ISP.
Many Registries have done this too, and it's quite common for TLD
Operators to provide such resolution services for their TLDs by
providing a wildcard redirect to a page showing that the domain is
available for registration along with a list of their accredited registrars.
Whereas there is nothing wrong with a TLD Holder's TLD Servers providing
shtml and/DNS wildcard redirects to registration services (You have,
after all, sent an HTTP query to space within their TLD), there is much
debate whether it is okay for either an independant *Registry*, such as
NSI, or an ISP, such as HughesNet (been sending redirects to
found-not-help for sometime now) or Comcast (Just recently began doing
this) to hijack the request via their own DNS servers.
Again, the best policy is to refrain from using Non-Inclusive Name Space
Friendly ISP supplied DNS Servers - That just goes w/o saying anyway.
Many of these ISPs have even hijacked DNS redirecting users (cookie
based) to adverts - and that's really bad juju!
LW wrote:
Breaking: Comcast DNS Hijacking Goes Live
Read About It Here: http://tldreport.net/?p=50
------------------------------------------------------------------------
_______________________________________________
Public mailing list
[email protected]
http://tldainc.org/mailman/listinfo/public_tldainc.org
--
Bradley D. Thornton
Top Level Domain Association
http://TLDAinc.org
_______________________________________________
Public mailing list
[email protected]
http://tldainc.org/mailman/listinfo/public_tldainc.org
