MEPIS Community Forum

Wireshark says that I am. Here's a redirect example from Comodo.



Yes, after any change in servers I either restart my network or reboot entirely. My modem and router are both turned off at night.

I've used a variety of DNS servers. Some DNS servers redirect on errors, and some do not. If they redirect, it's usually to a page with advertising. If they do not redirect, then I get the standard Firefox error page.


My LAN works with all of them I've tried so far, except OpenDNS and Comodo Secure. Using either of those, my PC cannot see my other machines. I won't pretend to know exactly why that is. I'm using the Google servers at the moment, and they work fine.

Have you considered installing & running namebench. It's in the repos. Run as normal user & will give you the best server settings for your router.

Thanks for the hint. It says I should be using Google 8.8.8.8 and 8.8.4.4, which happen to be what I have at the moment.

I've used Namebench last night and the results indicated that one of Talktalk's servers in the UK was best suited for my primary DNS but as its Talktalk's servers preventing me accessing Distrowatch, there's little point in using it.

Since switching from Auto detect to Google's 8.8.8.8 / 8.8.4.4 a few days ago, I believe I've seen an improvement with both Firefox, Opera and Thunderbird - I can certainly get to Distrowatch.

How did you establish that Talktalk was the problem? Have you run traceroute? Go to settings >> network assistant >> diagnosis, type in Distrowatch.com in the url window of traceroute & run to confirm its where the problem is.

chippy52,

Did as you advised and with my Router set to Auto DNS to go to my ISP's servers (Talktalk), there was no feedback back from traceroute for distrowatch.com.

Switching back to Google 8.8.8.8 / 8.8.4.4, no problem getting to distrowatch.com.

I was prompted to switch to Google DNS from a posting I read on Talktalk's forum.

Ref: http://www.talktalkmembers.com/forums/s ... hp?t=74834

That's best I can advise.

I played with it last night, and got 3 different sets of results for recommended DNS servers when running it 3 times in a row. lol

So, current network and dns server load, and when you run it probably has a big impact on the results you get.

Interestingly, one of the OpenDNS servers was fastest for me during one run, and one of the Google DNS servers was fastest another run, with one of the OpenDNS servers (not always the same one) showing up in the top results on all 3 runs of namebench I tried.

Here's one of the reports from it:

http://dl.dropbox.com/u/4536228/nameben ... _1846.html

When you ran traceroute where did it stop? What i'm getting at is, your router would be #1, ISP #2 etc. When run on my machine I go through 21 servers to get to Distrowatch.com. This is the final entry ( 21 ded135-fbsd-174-35.netsonic.net (66.180.174.35) 247.546 ms 247.838 ms 241.177 ms )

When I tried Traceroute with the router set to Auto DNS (talktalk) there was no entries at all for distrowatch.com

The Namebench site says that your first run is likely to be the most relevant for overall use. Repeating the run is likely to pull in local caches of pages, distorting the speeds.

Phil