Quantcast
Viewing all articles
Browse latest Browse all 19115

0007864: PEERDNS=yes required for DNS1 to be used in /etc/sysconfig/sysconfig/network-scripts/ifcfg-eth0

Not sure if this is a documentation bug or a Centos bug (I guess that is a matter of interpretation), but here:<br /> <br /> <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Using_the_Command_Line_Interface.html#sec-Configuring_a_Network_Interface_Using_ifcg_Files">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Using_the_Command_Line_Interface.html#sec-Configuring_a_Network_Interface_Using_ifcg_Files</a> [<a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Using_the_Command_Line_Interface.html#sec-Configuring_a_Network_Interface_Using_ifcg_Files" target="_blank">^</a>]<br /> <br /> it says "To configure an interface to use particular DNS servers, set PEERDNS=no as described above and add lines as follows to the ifcfg file: "<br /> <br /> This is incorrect, /etc/resolv.conf will *only* be updated with the value of DNS1 if PEERDNS=yes.<br /> <br /> So for the documentation to be correct it would need to read "To configure an interface to use particular DNS servers, set PEERDNS=yes as described above and add lines as follows to the ifcfg file: "<br /> <br /> even if that does mean PEERDNS now has a confusing name

Viewing all articles
Browse latest Browse all 19115

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>