Red Hat Bugzilla – Bug 819635
Fix help string for DNS zone --forwarder option
Last modified: 2015-05-20 11:32:33 EDT
This bug is created as a clone of upstream ticket: https://fedorahosted.org/freeipa/ticket/2717 Fix help of `--forwarder` option in per-zone configuration. Current help mentions "global forwarder", but this term is used rather for the list of forwarders in global DNS configuration and not for per-zone conditional forwarding: {{{ # ipa dnszone-mod --help Usage: ipa [global-options] dnszone-mod NAME [options] ... --forwarder=STR A list of global forwarders. A custom port can be specified for each forwarder using a standard format "IP_ADDRESS port PORT" # ipa dnsconfig-mod --help Usage: ipa [global-options] dnsconfig-mod [options] ... --forwarder=STR A list of global forwarders. A custom port can be specified for each forwarder using a standard format "IP_ADDRESS port PORT" }}}
Fixed upstream: master: https://fedorahosted.org/freeipa/changeset/52a9eb7a9c4673c6ce927a209833f2c35ffb70ed
automated regression test in DNS test suite
Testing using ipa-server-3.0.0-11.el6.x86_64 # ipa dnsconfig-mod --help Usage: ipa [global-options] dnsconfig-mod [options] Options: -h, --help show this help message and exit --forwarder=STR A list of global forwarders. A custom port can be specified for each forwarder using a standard format "IP_ADDRESS port PORT" <snip> Verified help for dnszone-mod # ipa dnszone-mod --help Usage: ipa [global-options] dnszone-mod NAME [options] <snip> --forwarder=STR A list of per-zone forwarders. A custom port can be specified for each forwarder using a standard format "IP_ADDRESS port PORT" <snip>
The dnszone-mod fix was all that was called for. dnsconfig-mod sets global forwarding. This appears fixed to me.
Namita, do you agree? Rob can you bounce it back?
Namita, Rob is right. dnsconfig --forwarder option contains a global DNS forwarder, dnszone --forwarder contains a per-zone forwarder.
Marking verified. Help for dnszone-mod is updated as expected.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0528.html