How to troubleshoot DNS problems?
Domain Name System (DNS) is a database system that translates a computer's fully
qualified domain name into an IP address.The DNS makes it possible to assign domain names to organizations independent of the routing of the numerical IP address. In other words, DNS is a system that translates domain names into IP addresses. This is necessary because computers only make use of IP addresses yet we use only human readable names since the names are easier to remember than IP addresses.
Setting up DNS in your network does not necessarily require you to become an expert DNS administrator. Setting up a DNS server typically involves configuring the DNS server with DNS zones to administer the DNS domain names in a
network, adding DNS resource records for the hosts in your network to your DNS zones, and delegating administration for these zones by creating a delegation from the parent DNS server previously authoritative for a domain name to the child DNS server that is accepting responsibility for a domain name. Lastly, a DNS server administrator should maintain the integrity of DNS zone data by securing the DNS servers in the network. You can also set up a DNS server from the command line. For more information
To correct DNS settings and troubleshoot DNS problems, you can
Run nslookup from a command line is the default dns server the one you expect.
use ipconfig /all on client to make sure the client point to correct DNS server and the the DC server points to only itself for DNS by its actual tcp/ip address, and make sure no any ISP DNS listed in tcp/ip properties of any W2K/XP.
When the machine loads it should register itself with the DNS. If not, use ipconfig /regiesterdns command.
Check Event Viewer to see whether the event logs contain any error information. On both the client and the server, check the System log for failures during the logon process. Also, check the Directory Service logs on the server and the DNS logs on the DNS server.
Use the nltest /dsgetdc: domainname command to verify that a domain controller can be located for a specific domain. The NLTest tool is installed with the Windows XP support tools.
If you suspect that a particular domain controller has problems, turn on the Netlogon debug logging. Use the NLTest utility by typing nltest /dbflag:0x2000ffff at a command prompt. The information is logged in the Debug folder in the Netlogon.log file.
Use DC Diagnosis tool, dcdiag /v to diagnose any errors. If you still have not isolated the problem, use Network Monitor to monitor network traffic between the client and the domain controller.
Under the following situations you may want to reinstall the DDNS in a Windows 2000 Active Directory:
Some weird DNS errors have occurred and clearing DNS information has been unsuccessful.
Services that depend upon DNS, such as, the File Replication service (FRS) and/or Active Directory are failing.
The secondary DNS server doesn't support dynamic updates.
To reinstall the dynamic DNS in a Windows 2000 Active Directory
Clear the DNS information.
Clear the Caching Reslover.
Point all DNS servers to the first DNS server under TCP/IP properties.
Re-add the zones and configure them to be Active Directory integrated.
Register a resource record for DNS as well as your start of authority (SOA).
How to troubleshoot DNS problems?
By: Techs24x7.com
Extracurricular Activities: Model Crime Investigation Buy a Water Tank Carefully After Looking Through Various Options Cafe World Experience Guides - Get It Now! Ошибки В Тренажерном Зале Introductions Of Custom Fitted Hats Cafe World Item Guides - Get Them Now! Как Выбрать Обои И На Что Нужно Обращать Внимание? Why Didn't My Accountant Tell Me That? Все О Фрилансерах-Переводчиках What Goes Into Being A Good Manager Тандем - Нотариус И Переводчик Que Trouve-T-On Dans Une Droguerie ? Waldenstrom