Bug 20900 - __res_maybe_init doesn't work with DHCP
Summary: __res_maybe_init doesn't work with DHCP
Status: RESOLVED DUPLICATE of bug 984
Alias: None
Product: glibc
Classification: Unclassified
Component: nss (show other bugs)
Version: 2.25
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-01 17:24 UTC by H.J. Lu
Modified: 2016-12-05 08:07 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-

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

Note You need to log in before you can comment on or make changes to this bug.
Description H.J. Lu 2016-12-01 17:24:44 UTC 
On Fedora 24, there is

[hjl@gnu-6 ~]$ ls -l /etc/resolv.conf 
lrwxrwxrwx 1 root root 35 Nov 30 11:44 /etc/resolv.conf -> /var/run/NetworkManager/resolv.conf
[hjl@gnu-6 ~]$ 

Before NetworkManager starts DHCP, /var/run/NetworkManager/resolv.conf
doesn't exist and the content of /etc/resolv.conf may change over time.
But __res_maybe_init never checks if /etc/resolv.conf changes.  When a
daemon process starts before DHCP or /var/run/NetworkManager/resolv.conf
is changed by DHCP, the daemon process gets the wrong DNS results.
Comment 1 H.J. Lu 2016-12-01 19:34:35 UTC 
Dup.

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