9 replies
by tejota
by support
by kevinknaul
by support
by burcjo
DNS is a program based on simple concepts but can be very difficult to troubleshoot at times.
All the local workstations need to have the IP address of your new dns server in their ip properties for them to resolve the names of remote named servers. If your new dns server contains cached entries (in dnsadmin)of the remote named servers you are pinging, then your dns server is configured correctly and should resolve those names to your workstations. Verify that there isn't a hosts or an lmhosts file on the workstations. Verify you're using the FQDN (according to the DNS server) or verify the suffix settings in the workstations IP Properties.
My first step in troubleshooting dns is from an NT workstation or another NT server, where I run the NSLOOKUP program from the command prompt. It tries to attach me to the name server I have listed in PRIMARY DNS Server settings in IP Properties. If I get an error indication at that point I need to verify that the machine I'm on has the correct Primary dns ip and that the primary dns server has a correct "NS" record and a correct "A" record that points to itself. If nslookup connects properly then from within the nslookup program I can try resolving names from there. If I can't resolve the names from within the NSLOOKUP program, then the configuration of the dns server is incorrect. If this local DNS server is configured to be a SLAVE then the Master DNS server should be checked to verify that it will supply the new DNS server with the records from that domain.
by support
by james_randy
by support
by support
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending