From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6)
Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2
Description of problem:
Connecting to Internet via Wireless, with PPTP VPN.
After update from NetworkManager.i386 0.3.3-1.cvs20050119.2.fc3, ftp,
ping, curl, wget are unable to resolve hostnames. However, telnet and
yum resolve hostnames correctly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. NetworkManager running
2. Connect to Wireless Network and run PPTP.
Actual Results: New DNS servers added to /etc/resolv.conf correctly.
Telnet, yum resolve hostnames correctly and can connect to remote servers.
FTP, ping, curl, firefox etc. do not resolve hostnames and are unable
to connect unless IP entered.
pptpconfig modifies /etc/resolv.conf, and I am assuing NetworkManager is unaware
of the changes to DNS.
More than likely you're correct. In the perfect world, only NetworkManager should touch resolv.conf
since it may be using caching nameserver configuration which would be destroyed by pptpconfig.
pptpconfig must execute a script of some sort to modify resolv.conf maybe? if so, this script needs to
be changed and we need to add an API to NetworkManager to allow other programs like pptpconfig and
VPN clients to update DNS information via NetworkManager.
I'm going to punt to pptpconfig, it should be a bit more intelligent about
modifying resolv.conf. But if you run pptpconfig after connection to a wireless
network, and close the connection before changing networks, you shouldn't run
pptpconfig's script should run 'nscd -i hosts' after it touches /etc/resolv.conf
and that may make most utilities aware of the changes.