|
|
Recent Articles |
CRM Installing, Implementing and Customization...
The application can be hosted, meaning it can be accessed through the web and there is no need for software or servers maintenance, or installed, meaning access to it is possible through a web interface...
Do I Need Certifications Before Starting A Computer...
I wish to start my own computer repair service, i don't have any certs in that field, but i know what each piece of hardware is called and where it goes etc, should i get any certifications before it think about starting...
Benefits Of Linux Training & Certification
Those IT professionals who can describe themselves as fans of open source operating systems and wish to enhance their skills by learning technologies other than Microsoft, will find that exploring the Linux world...
MCSE Certification: Real Boot Camps And Cheat Camps
A technical training school that provides accelerated instruction leading to MCSE certification is typically referred to as an MCSE boot camp. From my experience, having taught boot camps for five years, the name...
The EIGRP Adjacency
EIGRP is an important part of real-world networking as well as being a major topic
on the 642-901 CCNP BSCI exam. As with any networking topic, before you try to master intermediate and advanced skills, you...
|
|
|
08.31.07
On DNS Troubleshooting
 By
A.P. Lawrence
DNS problems can cause all sorts of strange network behavior.
Not being able to resolve Internet host names is an obvious symptom, but because of reverse lookups, general server slowness can be caused by the same thing.
Your server tries to look up a host name for a local machine trying to connect to it; if it takes too long, the other machine can give up.
Often machines are configured to use the ISP's DNS server, which of course knows nothing about local machines.
As long as it returns failure quickly, that's no problem: the server will continue on to look in its local files or its local DNS server.
Sometimes the ISP's server isn't actually broken, but simply takes too long to respond, causing timeouts or extreme delays locally.
On a Unix or Linux box, DNS servers can be easily tested at the command line.
Let's pretend your ISP DNS is 61.2.3.4:
dig @61.2.3.4 192.168.2.3
If that doesn't return quickly, local machines could experience problems. However, that test may not be enough to prove the issue.
The absolute test is to change your configuration to take the ISP server right out of your configuration.
If you comment out the nameserver in /etc/resolv.conf and local server issues improve, there obviously is a problem and it probably isn't at your end.
*Originally published at APLawrence.com
About the Author:
A.P. Lawrence provides SCO Unix and Linux consulting services http://www.pcunix.com
|
