Invalid PTR record created when you save a system entry
When you manage a DNS zone in FD (example, the network is 10.10.0.0/16), PTR records are created, relative to the 10.10.in-addr.arpa zone (ex IP 10.10.5.10 has an entry relativeDomainName=10.5). If one of these DNS entries correspond to a system declared in FD, the box "Enable DNS for this device" is selected. But if you make a modification on this system (add a service, change the description etc...), even if you do not touch the DNS part, when you save, it'll create another PTR entry, which is invalid like relativeDomainName=10.5.10.10 (not relative to the 10.10.in-addr.arpa zone). Once this bogus entry exists in LDAP, you cannot add other DNS entries, because FD says PTR records must be uniq, you have to remove the bogus relativeDomainName entry directly in the LDAP tree
(from redmine: issue id 2680, created on 2013-08-28, closed on 2013-08-28)
- Relations:
- duplicates #2636 (closed)
- Custom Fields:
- Bug in version: 1.0.6
- Uploads: