Bug 11815 - DNS2=xxxx not in /etc/resolv.conf
Summary: DNS2=xxxx not in /etc/resolv.conf
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-11-29 00:19 CET by Bit Twister
Modified: 2017-01-23 19:37 CET (History)
0 users

See Also:
Source RPM: resolvconf-1.74-3.mga4.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2013-11-29 00:19:40 CET 
Description of problem:

Second dns nameserver not in /etc/resolv.conf

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


How reproducible: Always


Steps to Reproduce:
1. Add second name server to nic configuration file 
2. systemctl restart network
3. cat /etc/resolv.conf

$ grep -i dns /etc/sysconfig/network-scripts/ifcfg-*
/etc/sysconfig/network-scripts/ifcfg-enp3s0:DNS1=127.0.0.1
/etc/sysconfig/network-scripts/ifcfg-enp3s0:DNS2=8.8.8.8

$ grep -v ^# /etc/resolv.conf
nameserver 127.0.0.1
search home.test


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-11-29 20:27:30 CET

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Comment 1 David Walser 2013-12-12 23:58:48 CET 
It won't solve the problem you're reporting, but for that configuration, if you are running a local nameserver, it'd probably make more sense to put 8.8.8.8 as a forwarder in your named.conf rather than list it as a second name server in resolv.conf.
Comment 2 Bit Twister 2013-12-13 07:54:57 CET 
(In reply to David Walser from comment #1)
> It won't solve the problem you're reporting, but for that configuration, if
> you are running a local nameserver, it'd probably make more sense to put
> 8.8.8.8 as a forwarder in your named.conf rather than list it as a second
> name server in resolv.conf.

Reason for second nameserver is for when first nameserver is not responding.

The better workaround is to put second nameserver in 
/etc/resolvconf/resolv.conf.d/tail   :)
Comment 3 David Walser 2013-12-13 16:26:25 CET 
(In reply to Bit Twister from comment #2)
> Reason for second nameserver is for when first nameserver is not responding.

I'd rather figure out why it's not responding and fix that :o)

> The better workaround is to put second nameserver in 
> /etc/resolvconf/resolv.conf.d/tail   :)

Yep, that works too.

CC: (none) => luigiwalser

David Walser 2013-12-13 16:26:33 CET

CC: luigiwalser => (none)

Comment 4 Samuel Verschelde 2015-04-23 14:03:26 CEST 
Is this bug still valid in Mageia 4 and / or cauldron?
Comment 5 Bit Twister 2015-04-23 20:40:18 CEST 
(In reply to Samuel VERSCHELDE from comment #4)
> Is this bug still valid in Mageia 4 and / or cauldron?

yes.
Comment 6 Bit Twister 2015-07-01 10:34:12 CEST 
Just verified problem is valid in release 5.
Samuel Verschelde 2015-07-01 12:20:34 CEST

Summary: 4_b1: DNS2=xxxx not in /etc/resolv.conf => DNS2=xxxx not in /etc/resolv.conf
Whiteboard: (none) => MGA5TOO

Comment 7 Bit Twister 2017-01-23 19:37:52 CET 
appears to be working in 6 sta2

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.