The DNS plugin fails to find the primary server, if it's in another zone

Greetings,

Let's assume the following configuration:

One DNS Server named "dns1"

One forward-zone named "example.com.", configured from FusionDirectory, as follows: $ORIGIN example.com. $TTL 300 @ 300 IN SOA dns1.example.com. postmaster.example.com. ( 2017053003 ; serial number 43200 ; refresh 900 ; retry 1814400 ; expire 7200 ; minimum TTL ) NS dns1.example.com. NS dns2.example.com. dns1 IN A 192.168.1.9

Another forward-zone named "subdomain1.example.com.", configured from FusionDirectory, as follows: $ORIGIN subdomain1.example.com. $TTL 300 @ 300 IN SOA dns1.example.com. postmaster.example.com. ( 2017053011 ; serial number 43200 ; refresh 900 ; retry 1814400 ; expire 7200 ; minimum TTL ) NS dns1.example.com. host1 IN A 192.168.1.10

When refreshing the "example.com." zone, we get a success message:

Ldap2Zone called for zone "example.com."

When refreshing the "subdomain1.example.com." zone, however, we are greeted with the following error:

Could not find the primary server

At this point, I would like to mention that if we manually execute the following command on the dns1 server, the zone will be generated and function normally:

argonaut-ldap2zone --verbose "subdomain1.example.com."

Best regards.

(from redmine: issue id 5560, created on 2017-05-31, closed on 2017-06-15)

• Changesets:
  • Revision fe96204f by Côme Chilliet on 2017-06-01T08:53:10.000Z:

Fixes #5560 Base primary server search on a records to be able to find it even in a other zone

• Revision c01d4a6f by Côme Chilliet on 2017-06-01T08:54:49.000Z:

Fixes #5560 Base primary server search on a records to be able to find it even in a other zone

• Revision 24589bcf by Côme Chilliet on 2017-06-01T09:48:06.000Z:

Fixes #5560 Read AAAA records as well to support IPv6

• Revision 6e2802bd by Côme Chilliet on 2017-06-01T09:48:38.000Z:

Fixes #5560 Read AAAA records as well to support IPv6

• Revision eb9e4fcd by Côme Chilliet on 2017-06-15T13:52:57.000Z:

Fixes #5560 Fixed an error on zone name sent to argonaut while refreshing

• Revision 487e097a by Côme Chilliet on 2017-06-15T14:43:57.000Z:

Fixes #5560 Changed the way the test is done to know if the server is the FQDN

• Revision 652e24d0 by Côme Chilliet on 2017-06-15T14:59:22.000Z:

Fixes #5560 Changed the way the test is done to know if the server is the FQDN

• Custom Fields:
  • Bug in version: 1.1
  • Support contract: None

Please disregard the "NS dns2.example.com." line in the example configuration, it slipped in by mistake.

(from redmine: written on 2017-05-31)

Applied in changeset commit:fusiondirectory-plugins|fe96204f.

(from redmine: written on 2017-06-01)

Applied in changeset commit:fusiondirectory-plugins|c01d4a6f.

(from redmine: written on 2017-06-01)

Applied in changeset commit:fusiondirectory-plugins|24589bcf.

(from redmine: written on 2017-06-01)

Applied in changeset commit:fusiondirectory-plugins|6e2802bd.

(from redmine: written on 2017-06-01)

If I try to refresh a zone from the dns object for example.com I have this.

Error: Request error: Error : Zone . was not found in LDAP!

If I try to do the subdomain1.example.com

Could not find the primary server

The two working if I do argonaut-ldap2zone example.com or subdomain1.example.com

(from redmine: written on 2017-06-15)

First error should be gone

(from redmine: written on 2017-06-15)

Applied in changeset commit:fusiondirectory-plugins|eb9e4fcd.

(from redmine: written on 2017-06-15)

Applied in changeset commit:fusiondirectory-plugins|487e097a.

(from redmine: written on 2017-06-15)

I don't see the buttons to refresh zones in the dns server directly.

(from redmine: written on 2017-06-15)

Close issue

(from redmine: written on 2017-06-15)

closed

added PJ1802-0188 and removed Bugs labels

added Fixed label