Hide Forgot
I've got eth1 interface with both ipv4 and ipv6 addresses. I'm trying to prepend another one DNS server by adding prepend domain-name-servers 8.8.8.8 ; to the corresponding config-file ( /etc/dhcp/dhclient-eth1.conf ). Everything is fine so far - I've got fully working /etc/resolv.conf : [root@work ~]# cat /etc/resolv.conf ; generated by /sbin/dhclient-script search example.ru nameserver 8.8.8.8 nameserver 192.168.0.6 nameserver 192.168.1.6 [root@work ~]# (I Removed actual IP addresses for two private DNS). Ok, now I'm trying to prepend IPv6 dns-resolver (public one, from Hurricane Electric) by adding the following line to /etc/dhcp/dhclient-eth1.conf : prepend domain-name-servers 2001:470:20::2 ; Ok, now restarting network with "service network restart" and all I get is two private dns: [root@work ~]# cat /etc/resolv.conf ; generated by /sbin/dhclient-script search example.ru nameserver 192.168.0.6 nameserver 192.168.1.6 [root@work ~]# and the following in my /var/lob/messages: Oct 18 16:40:25 work dhclient[10645]: /etc/dhcp/dhclient-eth1.conf line 1: semicolon expected. Oct 18 16:40:25 work dhclient[10645]: prepend domain-name-servers 2001: Oct 18 16:40:25 work dhclient[10645]: ^ Oct 18 16:40:25 work dhclient[10645]: /etc/dhcp/dhclient-eth1.conf line 1: expecting a statement. Oct 18 16:40:25 work dhclient[10645]: prepend domain-name-servers 2001:470:20::2 ; Oct 18 16:40:25 work dhclient[10645]: ^ Oct 18 16:40:25 work dhclient[10645]: /etc/dhcp/dhclient-eth1.conf line 3: semicolon expected. Oct 18 16:40:25 work dhclient[10645]: send Oct 18 16:40:25 work dhclient[10645]: ^
(In reply to comment #0) > prepend domain-name-servers 2001:470:20::2 ; correct is prepend dhcp6.name-servers 2001:470:20::2; (see dhcp-options(5) man page) but it seems that dhclient is really ignoring it. I'm trying to figure out what's wrong.
I asked upstream, but no response. https://lists.isc.org/pipermail/dhcp-users/2010-October/012126.html
I must admit that networking sub-system is really complex! I looked at the sources and sound something interesting (in /sbin/dhclient-script). I just added echo ${reason} right before "case "${reason}" in" in /sbin/dhclient-script and found that it gets PREINIT and REBOOT while has being configured for ipv4, but only PREINIT6 while has being configured for ipv6. The dhconfig function is called in case of "REBOOT" for ipv4 but dh6config is never called (no BOUND6|RENEW6|REBIND6|DEPREF6 parameter was ever passed to this script). I also looked at the dhcp client's sources and found that no BOUND6|RENEW6|REBIND6|DEPREF6 strings were ever hardcoded so dh6config have no chances to be called. So there are two possible issues - a) /sbin/dhclient-scrips is out of sync with dhclient (no BOUND6|RENEW6|REBIND6|DEPREF6 in dhclient) b) dhclient erroneously doesn't try to execute post-INIT hooks (REBOOT, in case of ipv4).
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Has already been fixed upstream https://source.isc.org/cgi-bin/gitweb.cgi?p=dhcp.git;a=commitdiff;h=a3471269e693cc4b49666874d5e57a6c9151b3b0 and will be part of 4.4.0 (currently in pre-alpha).