I try to go to StanJames today, but I can't.
Try to Ping Stanjames, i got this:
Pinging www.stanjames.com [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
WTF, the DNS server is saying that my computer (127.0.0.1) is Stanjames server. I then try to flush my DNS, edit my hosts file, doing stuff that an average network admin would do and try to go to StanJames site again....still the same thing. Hmmm, this is interesting.
To verify that it is not my ISP that having a wrong DNS entry, I try this online tool:
Lo and behold, this is what i got:
Retrieving DNS records for www.stanjames.com...
DNS servers
pdns1.ultradns.net
pdns2.ultradns.net
pdns3.ultradns.org
pdns4.ultradns.org
pdns5.ultradns.info
pdns6.ultradns.co.uk
Answer records www.stanjames.com
1A 127.0.0.11 20s
Authority records
....................
It is so clear that somebody has hijacked/poisoned stanjames DNS
server and put in the wrong IP address (127.0.0.1).
THe bottom line is I can't do some live bets today. I don't know when will they fix it but this is very interesting.
Try to Ping Stanjames, i got this:
Pinging www.stanjames.com [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
WTF, the DNS server is saying that my computer (127.0.0.1) is Stanjames server. I then try to flush my DNS, edit my hosts file, doing stuff that an average network admin would do and try to go to StanJames site again....still the same thing. Hmmm, this is interesting.
To verify that it is not my ISP that having a wrong DNS entry, I try this online tool:
Lo and behold, this is what i got:
Retrieving DNS records for www.stanjames.com...
DNS servers
pdns1.ultradns.net
pdns2.ultradns.net
pdns3.ultradns.org
pdns4.ultradns.org
pdns5.ultradns.info
pdns6.ultradns.co.uk
Answer records www.stanjames.com
1A 127.0.0.11 20s
Authority records
....................
It is so clear that somebody has hijacked/poisoned stanjames DNS
server and put in the wrong IP address (127.0.0.1).
THe bottom line is I can't do some live bets today. I don't know when will they fix it but this is very interesting.