Linux PC not getting name service
 

I have a PC set up to dual-boot Win2k and Red Hat 8.0. My organization just got its own domain and class C service. We have a dedicated box providing web, mail, and DNS service, and its running on all cylinders. I had no problem configuring Win2k to use the new static IP address, gateway, subnet mask, and DNS servers. But after installing RH 8.0 on a second disk, I can ping out to other machines but I'm not getting any name service under Linux.

Setup:
> Intel box running RH 8.0
> static IP address on a LAN w/ class C domain
> PC has a single Fast Ethernet connection to LAN
> a local machine runs BIND, sendmail, Apache
> have local machine as primary DNS, outside machines for secondary and tertiary
> ipchains appears to be running (I didn't want it, but that's what Anaconda wants me to have), I made sure everything is allowed

Symptoms:
> from Linux I can ping other machines inside our router
> from Linux I can ping the server box which is running BIND
> when running Linux I don't get any name resolution when using ping or nslookup, even when specifying 1st, 2nd, or 3rd nameserver numerically on nslookup command line
> an SGI workstation on the LAN gets name service OK
> from my PC running Win2k I get name service OK; can ping, nslookup, surf web etc.

I am stumped. It can't be the DNS server, other machines get name service just fine. Can't be the PC itself or its network connection, as everything works fine when running Win2k. The ethernet device definition in Linux must be OK, since I can numerically ping other local machines when running Linux.

What the heck is going on?

Add your names servers IP address to the /etc/resolv.conf. Also
make sure that there is no firewall running (stop iptables/ipchains).

does your resolv.conf have your domain entered

domain <domain name>
nameserver <ip address>

check iptables. Lokkit probably didn't do it, but often it will add something like

-A RH-Lokkit-0-50-INPUT -p udp -m udp -s xxx.xxx.xxx.xxx --sport 53 -d 0/0 -j ACCEPT (xxx.xxx.xxx.xxx being your nameserver)

This will likely clear it up without disabling iptables altogether assuming that your problem is firewall related. You can just stop iptables and see if it starts working.

jeff

resolv.conf was OK (identical to other machines here), but I think iptables was hosing it. I fumbled around some with it and the DNS info started getting thru. Not sure what I did that made the difference, but I seem to be up and running.

thx