Named DNS Server Not Resolving Domain Short Names

jviera · 06-01-2009, 03:16 PM

I have a server running Fedora Core 4 and Named. The server itself resolves all of the network server short names just fine. The domain is tow.net and if I do nslookup on the server for whs1 it comes back with whs1.tow.net and the correct address.

However, when using a Windows machine and doing an nslookup it says the domain doesnt exist when I use the short name... however if I do nslookup using the full whs1.tow.net it works. Why would a windows machine using this server not be able to get a correct nslookup on the short name but the server itself can?

archangel_617b · 06-01-2009, 04:02 PM

Quote:

Originally Posted by jviera

I have a server running Fedora Core 4 and Named. The server itself resolves all of the network server short names just fine. The domain is tow.net and if I do nslookup on the server for whs1 it comes back with whs1.tow.net and the correct address.

However, when using a Windows machine and doing an nslookup it says the domain doesnt exist when I use the short name... however if I do nslookup using the full whs1.tow.net it works. Why would a windows machine using this server not be able to get a correct nslookup on the short name but the server itself can?

This is an issue with the DNS resolver, the client, on the machine. Check your DNS settings on the client.

- Arch

technodweeb · 06-01-2009, 04:33 PM

If you are running windows to make the query from, go to the advanced TCP/IP settings and click on the Append the DNS suffixes. Then add tow.net. Then anything you try to lookup with DNS that does not have a FQDN will append the domain name you entered. If you are not using windows you will need to do something similar in that OS. I just made a guess on the windows.