A Records appear and disappear randomly Cause: Your DNS zone is configured to query WINS.

Can't logon or join the domain If DNS is not set up on the Domain controller correctly, domain-wide issues can occur such as replication between domain controllers. If DNS is not set up on th e client correctly, the client may experience many networking and internet issue s. Unable log on to the domain or join the domain from a workstation or server, and can't access the Internet indicate that you may have DNS settings issues. For consultants, refer to domain issue page. Can't open an external website using the same network domain name Create a DNS record for pointing to the www with the public IP. Common DNS settings mistakes 1.The domain controller is not pointing to itself for DNS resolution on all netw ork interfaces. Especially, when you have multihomed server, the WAN connection may be assign 127.0.0.1 as DNS ip. 2. The "." zone exists under forward lookup zones in DNS. 3. The clients on LAN do not point the DNS to internal DNS server. Can't find server name for ....: No response from server - DNS Request Timed Out Symptom: When running nslookup, you may receive this message: Can't find server name for ....: No response from server Cause: the DNS server's reverse lookup zones do not contain a PTR record for the DNS server's IP address. Refer to case 0204BL Can't Find Server Name for Address 127.0.0.1 when running nslookup Cause: You don't have a DNS server specified in your TCP/IP Properties. If you h ave no DNS server configured on your client, Nslookup will. default to the local loopback address. DNS issue with IP Filtering Symptoms: you have a windows 2000 server running IIS for public access with 10 p ublic IPs. The router is broken. We would like to enable IP filtering to block a ll ports except the port 80 for the web, 25 and 110 for the mail. After enabling IP Filtering, the server can't access any web sites, can't ping yahoo.com and n slookup gets time out. Cause: IP Filtering block the ports fro DNS. "DNS name does not exist." Cause: 1. Incorrect DNS. 2. The netlogon service tries to register the RR before the DNS service is up. R efer to case 0304TTa DNS on multihomed server It is not recommended to install DNS on a multihomed server. If you do, you shou ld restrict the DNS server to listen only on a selected address. If the multihom

ed computer are setup both NICs using the same IP range, for example, 192.168.0. 1/24 and 192.168.0.2/24, you will have a name resolution issue or connectivity i ssue. DNS request time out - ip name lookup failed When troubleshooting Outlook 550 5.7.1 relaying denied - ip name lookup failed b y using nslookup to resolve host name, you may receive "DNS request time out...*** Request to mail.chicagotech.net time -out. Possible causes: 1. Incorrect DNS settings. 2. Incorrect TCP/IP settings on the DC. 3. Missing PRT on Reverse Lookup Zones. Refer to case 0504BL DNS server can't access the Internet Symptoms: You have a domain controller with DNS. The server can ping router and any public IPs. However, the server can't open any web sites. Resolution: Check the server DNS settings, especially make sure the server point s to the internal DNS instead of the ISP DNS or 127.0.0.1. How to register the DNS RR 1. Go to DNS Manager to add it manually. 2. Use netlogon, ipconfig and nbtstat command. Refer to case 0304TTa How to troubleshoot DNS problems To correct DNS settings and troubleshoot DNS problems, you can 1) run nslookup f rom a command line is the default dns server the one you expect. 2) use ipconfig /all on client to make sure the client point to correct DNS serv er and the the DC server points to only itself for DNS by its actual tcp/ip addr ess, and make sure no any ISP DNS listed in tcp/ip properties of any W2K/XP. 3) When the machine loads it should register itself with the DNS. If not, use i pconfig /regiesterdns command. 4) Check Event Viewer to see whether the event logs contain any error informatio n. On both the client and the server, check the System log for failures during t he logon process. Also, check the Directory Service logs on the server and the D NS logs on the DNS server. 5) 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 Win dows XP support tools. 6) If you suspect that a particular domain controller has problems, turn on the Netlogon debug logging. Use the NLTest utility by typing nltest /dbflag:0x2000ff ff at a command prompt. The information is logged in the Debug folder in the Net logon.log file. 7) Use DC Diagnosis tool, dcdiag /v to diagnose any errors. If you still have no t isolated the problem, use Network Monitor to monitor network traffic between t he client and the domain controller. For consultants, refer to DNS issue page. How can I verify a computer DNS entries are correctly registered in DNS? A: You can use the NSLookup tool to verify that DNS entries are correctly regist ered in DNS. For example, to verify record registration, use the following comma nds: nslookup computername.domain.com.

How to add DNS and WINS into your Cisco VPN server If your VPN client cannot find servers or cannot ping computernmae, you may need to add DNS and WINS into your VPN server. For example, to add DNS and WINS on a Cisco Firewall PIX, add vpdn group 1 client configuation dns dnsservername and vpdn group 1 client configuration wins winsservername.. How to clear bad information in Active Directory-integrated DNS You may need to clear bad information in Active Directory-integrated if DNS is d amaged or if the DNS contains incorrect registration information. To do that, 1) Change the DNS settings to Standard Primary Zone. 2) Delete the DNS zones. 3) Use ipconfig /flushdns command. 4) Recreate the DNS zones. 5) Restart Net Logon service 6)Use ipconfig /registerdns How to ensure that DNS is registering the Active Directory DNS records To ensure that DNS is registering the Active Directory DNS records, to go DNS Ma nagement console>Server name>Forward Lookup Zones>Properties, make sure Allow Dy namic Updates is set to Yes and _msdcs, _sites, _tcp and _udp are correctly regi stering the Active Directory DNS records. If these folders do not exist, DNS is not registering the Active Directory DNS records. These records are critical to Active Directory functionality and must appear within the DNS zone. You should r epair the Active Directory DNS record registration.

Q: How does the internal DNS resolve names Internet without the ISP's DNS server A: As long as the "." zone does not exist under forward lookup zones in DNS, the DNS service uses the root hint servers. The root hint servers are well-known se rvers on the Internet that help all DNS servers resolve name queries. How to reinstall the dynamic DNS in a Windows 2000 Active Directory Under the following situations you may want to reinstall the DDNS in a Windows 2 000 Active Directory: Some weird DNS errors have occurred and clearing DNS information has been unsucc essful. Services that depend upon DNS, such as, the File Replication service (FRS) and/o r Active Directory are failing. The secondary DNS server doesn't support dynamic updates. To reinstall the dynamic DNS in a Windows 2000 Active Directory, 1. Clear the DNS information. 2. Clear the Caching Resolver. 3. Point all DNS servers to the first DNS server under TCP/IP properties. 4. Re-add the zones and configure them to be Active Directory integrated. 5. Register your A resource record for DNS as well as your start of authority (S OA). How to repair the DNS record registration To repair the Active Directory DNS record registration:

Check for the existence of a Root Zone entry. View the Forward Lookup zones in t he DNS Management console. There should be an entry for the domain. Other zone e ntries may exist. There should not be a dot (".") zone. If the dot (".") zone ex ists, delete the dot (".") zone. The dot (".") zone identifies the DNS server as a root server. Typically, an Active Directory domain that needs external (Inter net) access should not be configured as a root DNS server. The server probably needs to reregister its IP configuration (by using Ipconfig) after you delete the dot ("."). The Netlogon service may also need to be restar ted. Further details about this step are listed later in this article. Manually repopulate the Active Directory DNS entries. You can use the Windows 20 00 Netdiag tool to repopulate the Active Directory DNS entries. Netdiag is inclu ded with the Windows 2000 Support tools. At a command prompt, type netdiag /fix. To install the Windows 2000 Support tools: Insert the Windows 2000 CD-ROM. Browse to Support\Tools. Run Setup.exe in this folder. Select a typical installation. The default installation path is Systemdrive:\Pro gram Files\Support Tools. After you run the Netdiag utility, refresh the view in the DNS Management consol e. The Active Directory DNS records should then be listed. NOTE: The server may need to reregister its IP configuration (by using Ipconfig) after you run Netdiag. The Netlogon service may also need to be restarted. If the Active Directory DNS records do not appear, you may need to manually re-c reate the DNS zone.

After you run the Netdiag utility, refresh the view in the DNS Management consol e. The Active Directory DNS records should then be listed. Manually re-create th e DNS zone: Still need help, contact consultant Your feedback and contributions to this web site How to configure DNS Forwarders To ensure network functionality outside of the Active Directory domain (such as browser requests for Internet addresses), configure the DNS server to forward DN S requests to the appropriate Internet service provider (ISP) or corporate DNS s ervers. To configure forwarders on the DNS server: Start the DNS Management console. Right-click the name of the server, and then click Properties. Click the Forwarders tab. Click to select the Enable Forwarders check box. NOTE: If the Enable Forwarders check box is unavailable, the DNS server is attem pting to host a root zone (usually identified by a zone named only with a period , or dot ("."). You must delete this zone to enable the DNS server to forward DN S requests. In a configuration in which the DNS server does not rely on an ISP D NS server or a corporate DNS server, you can use a root zone entry. Type the appropriate IP addresses for the DNS servers that will accept forwarded requests from this DNS server. The list reads from the top down in order; if th ere is a preferred DNS server, place it at the top of the list. Click OK to accept the changes. For more troubleshooting information about DNS configuration for Active Director

y, see the following Microsoft Knowledge Base articles: DC's FQDN Does Not Match Domain Name Symptoms: After you promote or install a domain controller, the DNS suffix of yo ur computer name may not match the domain name. Or the FQDN does not match the d omain name because a NT 4.0 upgrade automatically clears the Change primary DNS suffix when domain membership changes check box. It is not possible to rename th e computer on the Network Identification tab. Also, you may receive NETLOGON eve nts in the System Log with ID:5781 or other error messages that indicate a failu re to dynamically register DNS records. Resolutions: 1. After you upgrade to Microsoft Windows 2000, but before you run dcpromo and obtain the Active Directory Installation Wizard, add the following v alues to the following registry key: Value name: SyncDomainWithMembership Value type: REG_DWORD Value: 1 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ 2. If you have already promoted to a domain controller, use the Active Directory Installation Wizard to demote to a member server. Click to select the Change pr imary DNS suffix when domain membership changes check box, and then run dcpromo to promote back to a domain controller. 3. Modify HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ and changed domain=mydomain.com, NV Domain=mydomain.com, SyncDomainWithMembersh ip= 1 (here mydomain.com is yhe donaim name). Primary or Active Directory Integrated DNS With Active Directory Integrated DNS, this permits all servers to accept updates . Instead of adding standard secondary DNS servers, you can convert the server f rom a primary DNS server to an Active Directory Integrated Primary server and co nfigure another domain controller to be a DNS server. With Active Directory Inte grated DNS servers, all the servers are primary servers, so when a zone change i s made at one server, it is replicated to the others, eliminating the need for a zone transfer. 2nd DNS Issues Setup Multiple DNS servers 1. When setup 2nd DNS, make sure you type correct Master DNS Server IP address. 2. Make sure primary DNS and 2nd DNS servers can ping each other and not firewal l block them. 3. Make sure primary DNS and 2nd DNS servers point to each other as primary and themselves as secondary if both DNS servers are in the same LAN. 4. If you have two or more DNS servers in different locations, each server shoul d point itself as primary and each other as secondary. Some A Records don't appear in DNS Cause: 1. incorrect TCP/IP settings. 2. Register this connection's address in DNS is unchecked. The DSA operation is unable to proceed because of a DNS lookup failure. Symptoms: 1. When trying to DCPROMO, ,you receive: "The operation failed because : The directory service failed to replicate off changes made locally. The DSA op

eration is unable to proceed because of a DNS lookup failure." 2. The Event Viewer may list Event ID: 1265 - The DSA operation is unable to pro ceed because of a DNS lookup failure. 3. DCDiag test display this message: "The DSA operation is unable to proceed be cause of a DNS lookup failure". Causes: 1. Incorrect TCP/IP configuration. 2. Incorrect DNS configuration 3. Bad information in DNS Manager. The procedure entry point DsIsManagedDnW could be located in the dynamic link lib rary NTDSAPI.dll Symptom: when trying to run DCDiag and getting the following error, "the proced ure entry point DsIsManagedDnW could be located in the dynamic link library NTDS API.dll". Resolutions: 1. Remove the dcdiag.exe from Controller Panel and install it from w2k/xp DC. 2. The "entry point not found" is typical of a service pack mismatch and the dcd iag.exe is out of sync with the service pack level of your system. To fix, go to the service pack x folder, and find "adminpack.msi" Right click it and select install. Troubleshooting the Domain Locator Process 1) Check Event Viewer on both the client and the DNS server for any errors. Verify that the IP configuration is correct for your network by using ipconfig / all. Ping both the DNS IP address and the DNS server name to verify network connectiv ity and name resolution. . Use nslookup servername.domain.com command to verify that DNS entries are correc tly registered in DNS. If nslookup command does not succeed, use one of the following methods to reregi ster records with DNS: a) force host record registration by using ipconfig /reg isterdns; b) force domain controller service registration by stopping/restarting the Netlogon service. If you still have the same issue, use Network Monitor to monitor network traffic between the client and the domain controller. Which DNS does a VPN client use 1. Assuming both LAN connection and VPN connection have the different DNS becaus e they are assigned by different DHCPs, the active DNS goes with the default gat eway. 2. You can pick up which DNS you want to use manually. Which ports are used for DNS UDP and TCP port 53. However, the internal DNS clients may not hear answers even though the query has been sent out on 53,until you open the UDP port above 1023 . Why I can't perform external name resolution to the root hint servers on the In ternet. A: make sure "." zone does not exist under forward lookup zones in DNS. If you d o not delete this setting, you may not be able to perform external name resoluti on to the root hint servers on the Internet.

Q: Why do I have to point my domain controller to itself for DNS? A: The Netlogon service on the domain controller registers a number of records i n DNS that enable other domain controllers and computers to find Active Director y-related information. If the domain controller is pointing to the ISP's DNS ser ver, Netlogon does not register the correct records for Active Directory, and er rors are generated in Event Viewer. The preferred DNS setting for the domain con troller is itself; no other DNS servers should be listed. The only exception to this rule is with additional domain controllers. Additional domain controllers i n the domain must point to the first domain controller (which runs DNS) that was installed in the domain and then to themselves as secondary. Why our web site doesn't work internally Q: Everyone can access our web site on the Internet. But no one can access the w eb site internally. Instead, we are point to our Intranet. A: If you network domain name is the same of your web site name, you should poin t the web to the web public IP. To do this, open DNS manager and create a host. for example www.chicagotech.net=public ip.