DNS Error

[Codec]

I'm getting "server DNS address could not be found" all the time when i try to visit some trackers/forums. How do i fix this?

[yoco]

Are you sure it's just you? I know I've had similar problems with TorrentBytes, couldn't open it for a month! It was something with my ISP!

[v6ph1]

I had the same problem during the last 2 days with sbi.

[Codec]

Are you sure it's just you? I know I've had similar problems with TorrentBytes, couldn't open it for a month! It was something with my ISP!

I get this error all the time. Sometimes it goes away after i refresh the page a few times. The whole day i was unable to enter this forum because of it. Is there anything that can be done to fix it?

[anon]

If you haven't done so already, try switching name servers to OpenDNS or Google Public DNS (if you trust them with your data). Also, change the negative response caching time to zero.

[Codec]

If you haven't done so already, try switching name servers to OpenDNS or Google Public DNS (if you trust them with your data). Also, change the negative response caching time to zero.

I have changed it to google dns. How to change negative response caching time?

[Instab]

we changed some network stuff which fixed the unfortunate network related problems some users encountered.

please do not use google or any other special dns. some dns servers update their records sooner than others. clearing your local dns cache is enough. the rest will settle automatically after some time.

[yoco]

I get this error all the time. Sometimes it goes away after i refresh the page a few times. The whole day i was unable to enter this forum because of it. Is there anything that can be done to fix it?

I thought I was the only one who had to refresh TB to open

[anon]

How to change negative response caching time?

Open a Command Prompt window as administrator and paste the following commands:

net stop Dnscache
reg add HKLM\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters /v MaxNegativeCacheTtl /t REG_DWORD /d 0x0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters /v NegativeCacheTime /t REG_DWORD /d 0x0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters /v NegativeSOACacheTime /t REG_DWORD /d 0x0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters /v NetFailureCacheTime /t REG_DWORD /d 0x0 /f
net start Dnscache
echo All done, press any key to exit...
pause > nul
exit

please do not use google or any other special dns. some dns servers update their records sooner than others. clearing your local dns cache is enough. the rest will settle automatically after some time.

Normally, I would also recommend against using "foreign" name servers (see this), but I get the feeling his provider's don't work well and that may be the cause of this problem.