Bug 507575 - Problem With The Second DNS Server
Summary: Problem With The Second DNS Server
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 10
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-23 11:11 UTC by Balogh Laszlo
Modified: 2009-06-24 08:52 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-06-24 08:52:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Balogh Laszlo 2009-06-23 11:11:52 UTC
Description of problem:

I experience a problem with Fedora 10. The second DNS server doesnt work.
I assign the network options via DHCP but the problem is the same with 
static IP.

I assign two DNS servers. One for my internal network (first one), and one external, that handles the ex-lan DNS (second one). NetworkManager receives the data right (nm-tool shows this.), i get the DNS servers assigned OK. I can ping names on the lan and from the internet OK from command line. 
But neither firefox nor the graphical package manager is able to connect to any outside DNS. I repeat: i can ping them from command line.

Funny thing: if i reverse the dns servers, making the external DNS1 and the internal DNS2 then the traffic from the internet works fine, but internal websites don't work. I can ping them from command line at the same time.

Resolv.conf holds the two dns servers all right.

If i disable NetworkManager and enable network services, the problem stays the same.

IPv6init=no

Version-Release number of selected component (if applicable):
I sighted the problem only on Fedora 10 X86_64, i386 installed after 2009.05.30.
I have working fedora 10 servers with the same config  - working all fine(although i havent updated them).  

How reproducible:
I just install Fedora 10......

Comment 1 Balogh Laszlo 2009-06-24 08:52:42 UTC
Hi there!

Sorry, Yum update and yum upgrade solved it.


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