Bug 829385 - [RFE] Add fake_mname option
Summary: [RFE] Add fake_mname option
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bind-dyndb-ldap
Version: 6.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Adam Tkac
QA Contact: Namita Soman
Depends On:
TreeView+ depends on / blocked
Reported: 2012-06-06 15:11 UTC by Dmitri Pal
Modified: 2013-11-21 20:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: New fake_mname bind-dyndb-ldap option which allows to override master server name in SOA record. Reason: Without this option it was impossible to share one LDAP database between multiple master servers. Only one master server could be used. Result (if any): With this optiopn it is possible to override master server name in SOA record so multiple servers can act as master server for one LDAP database.
Clone Of:
Last Closed: 2013-02-21 08:57:59 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0359 normal SHIPPED_LIVE bind-dyndb-ldap bug fix and enhancement update 2013-02-20 20:53:11 UTC

Description Dmitri Pal 2012-06-06 15:11:44 UTC
This bug is created as a clone of upstream ticket:

We should add an optional fake_mname option that would cause bind-dyndb-ldap to use the value of this option as mname for all queries it gets. We will basically pretend that the given server (most likely us) is the master for all the zones that we are serving.

Comment 1 RHEL Product and Program Management 2012-07-10 08:51:13 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 2 RHEL Product and Program Management 2012-07-10 23:06:31 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 3 Jenny Severance 2012-07-13 14:37:46 UTC
Please add description and use cases for this new option

Comment 4 Petr Spacek 2012-07-16 08:05:17 UTC
It is documented in http://git.fedorahosted.org/git/?p=bind-dyndb-ldap.git;a=blob;f=README

 fake_mname (default "")
         Ignore value of the idnsSOAmName (primary master DNS name) attribute
         and use this value instead. This allows multiple BIND processes to share
         one LDAP database and every BIND reports itself as a primary master in
         SOA record, for example.

Change "fake_mname" value in /etc/named.conf, reload named and try to dig SOA record to verify value seen by DNS clients.

Comment 5 Petr Spacek 2012-07-16 12:17:09 UTC
Worked example for existing zone "zone.example":

Zone is stored in LDAP object 'idnsname=zone.example,cn=dns,dc=e,dc=org'. It has attribute 'idnsSOAmName' with content 'ldap-value'.

Zone name is automatically added to fake_mname values without trailing period. If trailing period is present, value should be sent as is. (This applies to value in LDAP and value in /etc/named.conf in same way.)

1) Without fake_mname.
Delete fake_mname parameter from /etc/named.conf and reload named.

$ dig @ -t SOA +multiline zone.example
zone.example.		86400 IN SOA ldap-value.zone.example. nonexistent.zone.example. (

See column with text 'ldap-value.zone.example.'.

2) With fake_mname
Add fake_mname parameter to /etc/named.conf and reload named. Use the value 'override-value'.

$ dig @ -t SOA +multiline zone.example
zone.example.		86400 IN SOA override-value.zone.example. nonexistent.zone.example. (

3) With fake_mname and trailing period
Example for fake_mname value 'server.another-zone.example.':
$ dig @ -t SOA +multiline zone.example
zone.example.		86400 IN SOA server.another-zone.example. nonexistent.zone.example. (

Comment 12 Petr Spacek 2012-08-10 08:02:31 UTC
DNS dynamic updates are sent to "master" authoritative server, i.e. server declated in SOA mname field => all dynamic updates are sent to single server.

Fake_mname provides solution to this problem. It allows to announce more than one server as "master", i.e. distribute update requests across all servers.

Use case for this feature: To avoid single point of failure for dynamic updates.

Comment 13 Michael Gregg 2013-01-15 22:03:54 UTC
verified against ipa-server-3.0.0-9.el6.x86_64

dig @ -t SOA +multiline testrelm.com

testrelm.com.           86400 IN SOA zippyvm4.testrelm.com. hostmaster.testrelm.com. (

Comment 15 errata-xmlrpc 2013-02-21 08:57:59 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.