freeipa

#5580 ipa-client-install does not create a PTR record in existing reverse zone with enabled allow-sync-ptr
Closed: Invalid Opened by ofayans.

Closed: Invalid
Reopen Issue

I have a master instance with allow-sync-ptr enabled in global dns configuration.

The master has 2 zones configured: 

$ ipa dnszone-find
  Zone name: 122.168.192.in-addr.arpa.
  Active zone: TRUE
  Authoritative nameserver: master.pesen.net.
  Administrator e-mail address: hostmaster
  SOA serial: 1452086922
  SOA refresh: 3600
  SOA retry: 900
  SOA expire: 1209600
  SOA minimum: 3600
  Allow query: any;
  Allow transfer: none;
  Zone name: pesen.net.
  Active zone: TRUE
  Authoritative nameserver: master.pesen.net.
  Administrator e-mail address: hostmaster.pesen.net.
  SOA serial: 1452086939
  SOA refresh: 3600
  SOA retry: 900
  SOA expire: 1209600
  SOA minimum: 3600
  Allow query: any;
  Allow transfer: none;
----------------------------
Number of entries returned 2
----------------------------

When I install a client from the same subnet, I expect the master to automatically create a pointer dns record for it. However, it does not happen:

$ ipa dnsrecord-find 122.168.192.in-addr.arpa.
  Record name: @
  NS record: master.pesen.net.
  Record name: 63
  PTR record: master.pesen.net.
----------------------------
Number of entries returned 2
----------------------------

The corresponding A record is created allright:

$ ipa dnsrecord-show pesen.net. replica1
  Record name: replica1
  A record: 192.168.122.70
  SSHFP record: 4 2 75371CFAA8F43D5667EAA5207A96F60FC7993A443547ACB0CC796E83 90695A89, 1 2 366A8DB696558FABDBDFA22A916D6867F622EACF0C94FBCF7C3C9992 FDEE97B0, 3 2
                BBFDE72FC590775566E86EE276C9087D7D9016852BA23F402F68154E 59D1CE64, 1 1 B09090D1D94078EB044FA6475E3C62A4E60035F7, 4 1 8ED41236B37B410589230FC9E9C3C702BE71B45B, 3 1
                F9AF238811FC82E7694816540EF593DD7E599DC9

The packages were built yesterday from the upstream branch

Can you provide:

  1. ipa dnszone-find --all
  2. journalctl -u named-pkcs11
  3. client install log

As it turned out, it was a manually created reverse zone with dynamic updates disabled (they are disabled by default). With modifications described in https://fedorahosted.org/bind-dyndb-ldap/wiki/BIND9/SyncPTR the problem is gone. I am closing the ticket.

Metadata Update from @ofayans:
- Issue assigned to someone
Metadata
None
None
None
Normal
defect
IPA
None
0
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.