Bug 109578 - failed to detect provider's nameservers
Summary: failed to detect provider's nameservers
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-config-network
Version: 1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-11-09 20:27 UTC by Nikos Charonitakis
Modified: 2007-11-30 22:10 UTC (History)
0 users

Clone Of:
Last Closed: 2004-01-28 13:43:03 UTC

Attachments (Terms of Use)
screenshot of configuration dialog (35.49 KB, image/png)
2004-01-28 13:41 UTC, Harald Hoyer
no flags Details

Description Nikos Charonitakis 2003-11-09 20:27:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:
i tried to configure a dsl connection.
I entered:
provider's name, user name,password and accepted my pcmcia card probed
by the application.
I created the device and i tried to connect.
I pressed activate, everything went right and device was mentioned to
be up.
But no connection could be made reporting unknown hosts.
After that, i saw that nameservers of my provider were not in primary
dns and secondary dns boxes.
So i searched to /etc/ppp and i found that nameservers of my provider
were detected right in resolve.conf file.
My next action was to type these servers in primary,secondary dns boxes
and finally i ve connected to the internet.

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

How reproducible:

Steps to Reproduce:
1.configure dsl connection

Actual Results:  failure to connect to the internet

Expected Results:  connect

Additional info:

Comment 1 Harald Hoyer 2004-01-28 13:41:13 UTC
Created attachment 97297 [details]
screenshot of configuration dialog

Comment 2 Harald Hoyer 2004-01-28 13:43:03 UTC
as marked in the attachment, if you edit your DSL device, the options
for DNS should be checked.

Comment 3 David Balažic 2004-02-08 14:03:32 UTC
That option is enabled by default.
This looks like a duplicate of bug 109607.

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