|DNS seems to be messed up for my PC only|
| 2:47 pm on Aug 12, 2008 (gmt 0)|
Now for the second time in 8 days I experience a problem where I get a time-out error when trying to browse my NON-SSL sites. The only SSL site I have, and which uses another ip, works o.k.
It seems as if the problem only relates to my computer, or at least I have verified on other computers that they can still access these sites.
How can this be?
A ping reveals timeouts, so I cannot access the sites in any way other than try to connect via a proxy server to "cheat" the DNS. Really annoying as I cannot prepare orders or do anything, and it also leaves me with an uncertainty that this could be the same for an unknown number of other potential visitors.
Can this somehow be activated by something on my dedicated server? Last week my webhost wrote "He had flushed the iptables rules". Doesn't this indicate that this might somehow come from an erroneous command on my server?
| 11:41 pm on Aug 12, 2008 (gmt 0)|
Are you using Vista? I have two sites that keep timing out on my Vista machine.
| 12:39 am on Aug 13, 2008 (gmt 0)|
To be clear, have you tried another computer hooked up to your same modem/ISP connection? That is, is the problem related to your computer, or to the IP address assigned to your internet connection?
If it is your internet IP address, then a server-side problem is possible. If it is your computer, then likely there's something wrong in your computer itself -- perhaps some malware has tinkered with the settings in your 'hosts' file, or it could even be a computer-savvy buddy having a laugh at your expense... (not funny).
| 12:41 am on Aug 13, 2008 (gmt 0)|
Might be cached, have you tried Run -> ipconfig /flushdns
| 5:16 am on Aug 13, 2008 (gmt 0)|
I'm using XP-Pro, and the problem applies to all computers connected to our shared router.
The problem has remedied itself both times. First time it took ½ day and the next time 2 hours. I know positively that it is not due to that my ISP is blocking these sites, also I know that my ip-address has not been filtered out in my dedicated servers firewall.
The logical answer would be that the DNS-server I use has a problem, but 1) how could I find out if this is the case and 2) could I possibly workaround it?