Discussion Locked

DNS Server for name Resolution not doing

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I've setup a DNS server. I want my clients to use same. The DNS server I set up resides in one domain. It is connected to DNS servers in other domains on a WAN. If I ping by server name from a client on the local domain to a named server in another domain it responds with bad IP address. If I ping this same server from the DNS server I get a response. I do not want the clients to do DNS resolution else there would be no point in a DNS server to do this for me. MS says the DNS server is configured correctly.Good one? yes

9 replies

by tejota

If you can ping by host name from the DNS server, but not from a client/workstation, it sounds like the workstation does not have a DNS assignment. If you are running DHCP, make sure you have an entry for the DNS servers IP address to be handed outupon its lease renewal. Run WINIPCFG from 98 workstations and IPCONFIG from NT stations to determine whether the client workstations have a DNS assignment.

by support

I would have put this into the question but it does not allow the space. We have DHCP, the DNS server is handed out along with the IP address, we have wins servers, they are handed out with IP addresses. There is a DNS entry on the boxes that point to the DNS server

by kevinknaul

I would verify that you have the correct settings for DHCP in the client's setup. (ie. Use DHCP, DISABLE DNS) An verify that you are handing out the correct domain name with your client's DHCP IP address, as this will determine the where the serverresolves the name. I hope this helps...

by support

Okay-lets get to nitty gritty. There are multiple domains on a world wide network. Names are resolved locally no problem. When a client pings a name it tags on the domain so it is xxxx. domain.com What is occurring is because the name has the local tag it hits the local DNS server and the DNS server does route the request outside its boundries and searches only the local domain and therefore does not find xxxx where it really is. This is the issue gentlemen. When the query runs local on the DNSserver it finds it in other domains.

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 james_randy

Since your question is so old, you might as well just reload the latest versions of all software, and you'll have a new set of problems to deal with. Heck, update all your hardware and operating systems while you're at it. Have a real party.

This discussion is closed to new replies.