Have to use proxy site

[rynoman03]

If typing it in a browser doesn't work a traceroute won't work either because both tracert and web browsers use DNS to resolve the host names. To fix it either change your DNS or type in the IP of GPF to get here. In case any of you missed it, this is the IP of the GPF server: 207.58.151.196. Kthxbai!

But if people can't gain access to the site how are they going to know to type the IP in smarty pants.

But anywho...

Got home and it didn't work until I took the "www." off and just typed grandprixforums.net

You can use Google's Public DNS here... Using Google Public DNS

BTW GPF still has issues resolving...

The first two nslookups in step 3 Fail.... Not good.

This is quoted from google...

Step 2: Verify that Google Public DNS can resolve the selected hostname ie. www.grandprixforums.net

At the command prompt, run the following command, where hostname is the name that you were having difficulty resolving:

On Windows:

nslookup -debug hostname 8.8.8.8

On Mac and Linux:

dig @8.8.8.8 hostname

If the the output shows an answer section with an A record for the hostname, then Google Public DNS is able to resolve the name. Check your settings to make sure your system is correctly configured to use Google Public DNS. If you are still unable to solve the problem, please include the output of the command in any communication with the Google Public DNS team.

If the output does not show an answer for the hostname, continue to step 3.
Step 3: Verify that another open resolver can resolve the selected hostname

At the command prompt, run any one of the following commands, where hostname is the name that you were having difficulty resolving:

nslookup hostname 4.2.2.1

nslookup hostname 4.2.2.2

nslookup hostname 208.67.222.222

nslookup hostname 208.67.220.220

(The first two commands test Level 3's DNS servers. The last two commands test OpenDNS' DNS servers.)

If you are not able to get a successful result, this means that there is most likely a problem with the server you are trying to contact. Wait some time and try running the tests again. This may be a temporary problem on the server's side that will likely resolve itself eventually. If it does not, you should contact the owner of the server.