4:13 p.m.
Hello,
I have an odd issue that just cropped up... I've been using FreeIPA for the past two
or three months. I'm using it both for user/group membership as well as for internal
DNS.
Any time I try to add an A record with the "Create reverse" option checked, I
see the "waiting" message for about 30 seconds, then I get an error message that
the reverse record could not be created.
Here's an example:
Forward Lookup Zone:
company.com
Reverse Lookup Zones:
10.16.172.in-addr.arpa.
100.16.172.in-addr.arpa.
101.16.172.in-addr.arpa.
11.16.172.in-addr.arpa.
12.16.172.in-addr.arpa.
Let's say I go to add an A record for "test-record" in the company.com
forward lookup zone:
A -> 172.16.100.123
I see the "Waiting" message for roughly 30 seconds, followed by this error
message:
"Cannot create reverse record for "172.16.100.123": No answers could be
found in the specified lifetime for DNS reverse zone 123.100.16.172.in-addr.arpa."
It looks like FreeIPA is appending 123 to the zone name (123.100.16.172.in-addr.arpa.)
when it should be trying to create the PTR record in 100.16.172.in-addr.arpa.
This only happens with some of the Reverse Lookup Zones - it doesn't occur
consistently across all zones.
For example, I just tried creating a second entry for "test-record2" in
company.com:
A -> 172.16.10.124 (PTR should be in 10.16.172.in-addr.arpa.)
Both the A record and PTR record get created successfully.
Does anyone happen to have any thoughts as to why this may be happening?
I've been considering deleting the 100.16.172.in-addr.arpa. zone and recreating it,
but I have a few dozen records and would prefer to not have to create them again.
Thanks in advance!