Chrome screenshot depicts “nehe.gamedev.net” as opened on Croatian T-Com ISP with their DNS. Black Safari screenshot depicts “nehe.gamedev.net” when using Google’s DNS server.
Reportedly Croatian ISP B-Net also has the same issue.
On B-Net and T-Com, nehe.gamedev.net resolves to 22.214.171.124. Ordinarily it should resolve to 126.96.36.199.
White Safari screenshots depicts what you get when you visit this IP directly. Apparently searchmagnified is not owned by NetworkSolutions because it advertises other registrars.
Could this be some well orchestrated DNS hijack? Or is it just caching gone haywire? (It seems strange that this reputable domain would “revert” to a spyware and ad-troll site and be restored so quickly, but that Croatian ISPs’ DNSs’ would go insane.)
Could it be related to this January 2010 attack against Network Solutions?
From inquiring foreign acquaintances and friends, looks like this is a local problem. Also, here’s some whois and nslookup digging.
The-Evil-MacBook:~ ivucica$ whois gamedev.net
Bells & Whistles Software, Inc.
2705 North Carroll Avenue
Southlake, TX 76092
Domain Name: GAMEDEV.NET
Promote your business to millions of viewers for only $1 a month
Learn how you can get an Enhanced Business Listing here for your domain name.
Learn more at http://www.NetworkSolutions.com/
Administrative Contact, Technical Contact:
ZWave, LLC domains@ZWAVE.COM
2705 N CARROLL AVE
SOUTHLAKE, TX 76092-3101
(817) 329-9242 fax: (817) 329-9243
Record expires on 26-Mar-2020.
Record created on 26-Mar-1999.
Database last updated on 2-Apr-2010 12:59:27 EDT.
Domain servers in listed order:
The-Evil-MacBook:~ ivucica$ nslookup
> server 188.8.131.52
Default server: 184.108.40.206
Looks like the domain itself is pretty much doing very well! As it stands it looks like it’s truly a DNS hijack, but I’m not exactly a network expert so don’t take my word for it.
isto i na optimi o.O
We had the same thing happen today – a customers domain on our internal DNS resolver was pointed to the exact same IP – 220.127.116.11
I don't believe that this is an accident
I was wondering if you could provide some more insight:
* Was an ISP's caching DNS affected?
* Was the original domain's nameserver affected?
* If the cache was affected, did you try querying the domain's nameserver directly?
I'm just curious!