resolv.conf not updating

[lancherider]

I'm running FC4 on an IBM Thinkpad T42. It has an ethernet interface and a wireless interface. By default, the ethernet interface is what I use 90% of the time. However, I do occasionally connect to the wireless network at my office. Here's the problem:
When I shut down the ethernet interface (ifdown eth0) and then bring up the wireless interface (ifup eth1), dhclient is not updating the name servers in my resolv.conf file, so I can't resolve anything. I have connectivity and I receive an ip via dhcp, but I can only connect if I specify ip addresses. Both cards are configured to receive DNS information via DHCP, and as I said, I am being assigned an ip on the wireless network, but it won't automatically update resolv.conf with the wireless network name servers.
At first, I thought this was great because I didn't have the problem I see so many people complain about that they can't keep their resolv.conf settings from changing at reboot. Now, however, I'm realizing it's not as great as I thought. Any ideas?

[pparks1]

lancherider,

I believe that I had the exact same problem in FC4. My wireless would pull an IP, but would not update /etc/resolv.conf. I would have to add the name server manually, and then after I would connect back to wired LAN, my settings would be overwritten by DHCP and I would thus not get name resolution when I later attached via wireless.

I don't have my laptop with me right now to see if I documented any type of resolution. I'll let you know if I remember it. But just wanted to let you know that others have seen the same problem.