First a quick explanation of what is happening. The DNS system is basically like a telephone directory, where it looks up a human friendly name like google.com and translates it into the ip adress the computer actually needs, in this example 72.14.204.147.
What they have done is replaced that entry with an ip address belonging to a different computer, that is displaying that unfriendly message.
So to circumvent it you just need to inform your computer that there is a bad entry in the directory and that it should be ignored or to start pulling from a different directory.
Ok enough theory how does this work in practice? A quick fix would be to add the ip along with the hostname to your local 'hosts' file, which is a file that your computer consults first before going to your registered DNS provider (you have one, probably from our ISP whom in turn gets it from.... and so forth).
under linux this would be the "/etc/hosts" file.
under windows this would be the Windows directory"/system32/drivers/etc/hosts" file.
There you would then add the entry of interest, in the case of the google example above something like;
For more info see: http://en.wikipedia.org/wiki/Hosts_%28file%29
I have lots of entries in my host file, to avoid such things as the doubleclick domain, and to redirect some connections to my local machine instead of over the network to a machine I can't reach because of intervening firewalls.
E: "Did they... did they just endorse the combination of the JSDF and US Army by showing them as two lesbian lolicons moving in together and holding hands and talking about how 'intimate' they were?"
B: "Have you forgotten so soon? They're phasing out Don't Ask, Don't Tell."
What they have done is replaced that entry with an ip address belonging to a different computer, that is displaying that unfriendly message.
So to circumvent it you just need to inform your computer that there is a bad entry in the directory and that it should be ignored or to start pulling from a different directory.
Ok enough theory how does this work in practice? A quick fix would be to add the ip along with the hostname to your local 'hosts' file, which is a file that your computer consults first before going to your registered DNS provider (you have one, probably from our ISP whom in turn gets it from.... and so forth).
under linux this would be the "/etc/hosts" file.
under windows this would be the Windows directory"/system32/drivers/etc/hosts" file.
There you would then add the entry of interest, in the case of the google example above something like;
Code:
72.14.204.147 google.comFor more info see: http://en.wikipedia.org/wiki/Hosts_%28file%29
I have lots of entries in my host file, to avoid such things as the doubleclick domain, and to redirect some connections to my local machine instead of over the network to a machine I can't reach because of intervening firewalls.
E: "Did they... did they just endorse the combination of the JSDF and US Army by showing them as two lesbian lolicons moving in together and holding hands and talking about how 'intimate' they were?"
B: "Have you forgotten so soon? They're phasing out Don't Ask, Don't Tell."