Bug 172134 - Wired connections do not set nameserver?
Wired connections do not set nameserver?
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-10-31 14:01 EST by Andrew Overholt
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-31 14:40:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrew Overholt 2005-10-31 14:01:29 EST
Description of problem:
Wireless connections set up nameserver entries in /etc/resolv.conf for the
actual nameservers (by IP).  Wired connections just have 127.0.0.1 listed
(twice, incidentally) and name resolution does not work.

Version-Release number of selected component (if applicable):
NetworkManager-0.5.1-1.FC4.4
dhcdbd-1.9-1.FC4
bind-9.3.1-14_FC4
wireless-tools-28-0.pre10.5

How reproducible:
Always.

Steps to Reproduce:
1. Wireless connection ... works.
2. Wired connection ... connects but no name resolution

Additional info:
I think this is all the latest stuff from fc4-updates-testing.
Comment 1 Andrew Overholt 2005-10-31 14:40:35 EST
Restarting NM{,Dispatcher} and named seemed to do the trick.  I set named to
start on boot and after a reboot I have working IP resolution with a wired
connection.

Note You need to log in before you can comment on or make changes to this bug.