Bug 109607

Summary:	DNS doesn't work with xDSL unless addresses are manually entered
Product:	[Fedora] Fedora	Reporter:	Andre Robatino <robatino>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1	CC:	david.balazic, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-04-29 01:41:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andre Robatino 2003-11-10 05:34:32 UTC

Description of problem:
  After creating an xDSL connection with a fresh install of FC1, upon
connecting there is no name service.  The cause is that the DNS
addresses are automatically acquired and entered into
/etc/ppp/resolv.conf, but not into /etc/resolv.conf.  I worked around
this by manually entering the 2 DNS addresses under the DNS tab in
redhat-config-network.  I'm not sure whether initscripts is the right
component for this bug.

Version-Release number of selected component (if applicable):
initscripts-7.42-1

How reproducible:
always

Steps to Reproduce:
1.  Configure an xDSL interface.  Do _not_ enter the DNS addresses
manually, but let them be acquired automatically.
2.  Bring up the interface.
  
Actual results:
  No name service.  Must copy the DNS addresses which appear in
/etc/ppp/resolv.conf into redhat-config-network for them to be recognized.

Expected results:
  Should have name service without manually entering the DNS addresses.

Additional info:
  I reported this in bug #105748.

Comment 1 David Balažic 2004-01-10 20:00:53 UTC

Same bug here.

 - installed FC1
 - using redhat-config-network I set up and ADSL connection
 - works, except /etc/resolv.conf is not populated, have to do it
manually. /etc/pp/resolv.conf gets the correct data

Seems there are a lot of duplicates of this bug : 105748, 109578, 98786

Comment 2 David Balažic 2004-01-10 20:29:34 UTC

Renaming ( changing it's nick ) the xDSL connection to ppp0 supposedly
fixes the problem. I personally did not try it.

Comment 3 Jef Spaleta 2004-02-02 17:15:20 UTC


*** This bug has been marked as a duplicate of 109601 ***

Comment 4 David Balažic 2004-02-08 14:10:04 UTC

This is not a duplicate of bug 109601. It is not fixed by
initscripts-7.42.2-1

Here is what I did :
 - install FC1 fresh ( Personal Desktop minus Print Support and Office
Apps )
 - update everything to latest as of 7-feb-2004 ( including
initscripts-7.42.2-1 )
 - reboot
 - Start Menu -> System Settings -> Network -> New -> xDSL Connection
, enter Provider name, Login name and  Password, click Apply
 - reboot
 - log in as non-root into X
 - Start Menu -> System Tools -> Network Device Control -> Activate
hte xDSL connections

Results : everything works, except DNS as /etc/resolv.conf is empty.
After adding the line "nameserver 193.189.160.11" ( got server address
from /var/log/messages :
Feb  8 14:53:32 localhost pppd[6649]: primary   DNS address 193.189.160.11
Feb  8 14:53:32 localhost pppd[6649]: secondary DNS address 193.189.160.12
, everything works OK.

Comment 5 Bill Nottingham 2004-03-17 02:58:46 UTC

Is PEERDNS set in your ifcfg file?

Comment 6 David Balažic 2004-03-17 08:22:22 UTC

Can't check right now. I have everything as installed by fresh fedora
core test1 system. I haven't changed anything, just set up an xDSL
connection by that GUI tool. Then I also tried updating every packages
to latest versions as of 7-feb-2004 ( see above ).

Comment 7 Andre Robatino 2004-03-17 14:49:27 UTC

  PEERDNS=yes in mine.

Comment 8 Bill Nottingham 2005-04-29 01:41:55 UTC

Closing bugs on older, no longer supported, releases. Apologies for any lack of
response. Please reopen if this persists on current releases such as Fedora Core 3.