Description of Problem: After "ifup eth0" nameserver line in /etc/resolv.conf is broken Version-Release number of selected component (if applicable): initscripts-6.34-1 How Reproducible: always How it happens: [root@leon leon]# /sbin/ifup eth0 oPREDELQETSQ INFORMACIQ IP DLQ eth0... GOTOWO. (Russian :) [root@leon leon]# grep nameserver /etc/resolv.conf nameserver 19 [root@leon leon]# killall dhcpcd [root@leon leon]# dhcpcd[root@leon leon]# grep nameserver /etc/resolv.conf nameserver 193.178.236.130 nameserver 193.178.236.131 nameserver 213.130.10.10 Additional information: DHCP server 2.0pl5-4
Just to confirm, you are using dhcpcd?
Yes. I'm unable to reproduce this problem after system reboot - now everything is OK. Described situation happened when I changed IP information from static to DHCP and tried ifdown/ifup without reboot.
What did your resolv.conf look like when it was static?
(I can't reproduce this switching from a static to a dynamic IP address here.
During installation I configured the box for using 192.168.200.1. Now I have following: [leon@leon leon]$ vdir /etc/resolv.* -rw-r--r-- 1 root root 144 sEN 3 14:00 /etc/resolv.conf -rw-r--r-- 1 root root 44 sEN 1 15:23 /etc/resolv.conf.bak -rw-r--r-- 2 root root 41 sEN 3 12:29 /etc/resolv.conf.sv [leon@leon leon]$ grep nameserver /etc/resolv.conf.bak /etc/resolv.conf.sv /etc/resolv.conf.bak:nameserver 192.168.200.1 /etc/resolv.conf.sv:nameserver 19 BTW, I'm still unable to reproduce described situation.
I don't see anything in initscripts that writes ".sv" files, so I'm going to close this (since you also said you couldn't reproduce it.)
Yes, I'm unable to reproduce. May be closed