I'm running RH 9 at work and it seems my DNS entry is not working. I'm pointing to my corporate internal DNS server but it's still not resolving any internal device names. The same DNS server works properly for 1000+ other PCs so I know it's not a DNS server issue.

I checked following file contents, which seem correct:

resolv.conf
nameserver 10.200.10.200

host.conf
order hosts,bind


I can ping the DNS server by IP and all other devices by IP as well. If I enter some device name & IPs into the hosts file, only then can I ping them by name.

I have a feeling this problem is also screwing up my ability to map from Linux to Windows shares as that is also not working but worked for me before.

Any help is appreciated!!

"I'm pointing to my corporate internal DNS server but it's still not resolving any internal device names."

I think that you have to point at your DNS twice, once by letter name and once by number name. Try something like this:
resolv.conf
search corp.dns.net
nameserver 10.200.10.200

or perhaps:
resolv.conf
domain corp.dns.net
nameserver 10.200.10.200

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

I am just guessing here, but have you tired running dhclient __interface__ or dhcpcd __interface__, where __interface__ is the valid network interface that you are trying to connect through? It worked for me.

If it is a Windows network, are you sure that internal hostnames are being resolved via DNS, and not WINS?

hi,

here are some debug steps:

just type command

bash# dig.

It will give screen full of output. check the server ip. should be of form

;; SERVER: 10.200.10.200#53(10.200.10.200).

If its showing currect DNS ip address then type

bash# dig linuxquestions.org

this should show ipaddress of linuxquestions.org site.

Thanks for all the feedback, folks! Here's the results of testing.

jojuof,
The dig cmds you suggested worked, as you stated but still no internal resolution is working.

MS3FGX,
We are all DNS. We've retired WINS years ago.

sonajiso,
I ran /sbin/dhclient eth0 as root but that changed me from a static IP to DHCP assigned IP address, which I don't want (sorry , I didn't mention that previously). Regardless, that change didn't resolve the DNS problem.

---------------------------------------------------------------------------------------------------

While trying all of the above, I just found the problem but not sure how to fix it yet. From my Win PC, I see that i have a "primary dns suffix" of "us.myco" and a "connection-specific dns suffix" of "ny.us.myco" so when i try to ping from windows pc's to server1, it appends the us.nyco to the end and successfully resolves.

Now, from Linux, when I try to ping server1 along, it fails. If I ping server1.us.myco, it works. Some servers only work when I ping them via server2.ny.us.myco maybe because they're in a different site.

In either case, where/how can I enter the 2 suffix commands I listed above that are in my Win box into Linux? That should resolve my resolution problems!!

in your resolv.conf file

search us.myco ny.us.myco
nameserver 10.200.10.200

This will search in order first us.myco then ny.us.myco.

Thanks; that did it!!

I was entering them through the Network Config --> DNS Search Path but they weren't all working there. I must've been seperating them with the wrong character (using comma instead of space).

FYI, making this change broke my ability to reach websites (either through the browser or dig cmd). I had to reverse the order to resolve this problem. See my new resolv.conf contents below:

nameserver 10.200.10.200
search us.myco ny.us.myco