Hello Myzani,
Do you have the full test on the network error you are receiving, perhaps one of the errors listed below?
Network Error (tcp_error) A communication error occurred: 'No route to host' The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
For assistance, contact your network support team.
or,
Network Error (tcp_error) A communication error occurred: "" The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
For assistance, contact your network support team.
or,
Network Error (tcp_error) Error - Network Error (tcp_error), a communication error occurred and "Operation timed out " the webserver may be down or too busy or experiencing some other problems preventing it from responding to the requests. You may wish to try again at later time.
If so, you can always try flushing your DNS table by choosing Start, Run and typing CMD which brings you to the DOS Prompt (command line window). Once there, type ipconfig /flushdns
If you continue to have problems in Windows, you can turn off the DNS Cache (good only until you reboot, then it turns back on) by typing either one of these commands at the DOS Prompt (command line window)
net stop dnscache
sc servername stop dnscache
MAC OSX users can simply use the following command to flush their DNS cache.
lookupd -flushcache
Linus users can use the nscd daemon to control the the DNS cache.
To flush the cache, restart the nscd daemon which you do by using the command
/etc/rc.d/init.d/nscd restart
If this solves the problem, then you may want to know how to turn off (close to off as possible) the DNS Cache permanently. The DNS cache is controled in this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Dnscache\Parameters registry key. You'll have to set two values under this key, they are MaxCacheTtl and MaxNegativeCacheTtl.
MaxCacheTtl is the max time that the results of a DNS lookup will be cached and has a default of 86,400 seconds (24 hours). Setting this value to 1 tells the system to keep lookups in the cache of 1 second.
MaxNegativeCacheTtl tells the system to hold failed lookups for 15 minutes (900 seconds) and by setting it to 0, you are instructing the system to not cache failed DNS lookups at all.
BY the way, A DNS server matches the URL of a website (eg www.websecurity.mobi) with its numeric IP address - it translates www.websecurity.mobi into the unique numeric IP address (66.39.6.10). Whenever you request a web page, your browser asks the name server to find the numeric translation of the URL.
Without the DNS servers, it would be a complicated web because we would have to know all the IP addresses rather than the nice friendly name, like Websecurity.mobi or Google.com
Let me know if that helps!
Regards,
Jim.