Ok the hosts file is a local file that the OS checks first before it goes out into the world and asks for name resolution.
It is specific to the machine that it sits on. So I would suggest if you are comfortable with changing it, you change it on your main Supertenere surfing computer and see how it goes for a while.
On XP/Vista/Win7 you should find it on C:\Windows\System32\drivers\etc\
Or more correctly (%SystemRoot%\System32\drivers\etc\)
The file is called "hosts" and it is just a text file (like a real OS for a change).
It looks like..
-------------------------------------------------------------------------------------------
# Copyright (c) 1993-2006 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
::1 localhost
96.126.123.205
www.yamahasupertenere.com # Temp Super Ten host Entry for testing.
------------------------------------------------------------------------------------------------------------------------------------
That last line I added just so you should be able to copy and paste into Notepad.
In fact all you need in the file is anything that doesn't start with a #
Anything after a # is a comment.
So the usual proceedure is to copy the original into a safe place with a name like hosts_original or something.
Open up the hosts file in notepad and add .1 line..
96.126.123.205
www.yamahasupertenere.com # Temp Super Ten host Entry for testing.
and save.
You may have to be an administrator to do so. I always am so I forget what the procedure is if you are sensible and not running as an admin.
After that hopefully you will have reliable service.
If it is reliable you know it's something to do with your local DNS OR where it is getting it's info from.
From where I sit, it looks like your local dns has intermittent issues or the next jump along. Something is stored or cached somewhere. So I agree with the others to that extent, It's just we don't know where.
The rest of the world seems OK now. The problem seem intermittently local to you.
I was going to write a quick script t interrogate it at regular intervals to see whether it gave consistent results but it is inside your network so that doesn't look like it is possible.
I could try your ISP's DNS if you know what it is.
Anyway I'm off to get some beauty sleep now cause I really need it.
