freeipa

#8649 Resolving IP to reverse zone is broken
Closed: worksforme by carbenium. Opened by carbenium.

Closed: worksforme
Reopen Issue

Issue

Adding an "A" record and having "Create reverse" results in following error:

Cannot create reverse record for "192.168.1.107": DNS reverse zone 168.192.in-addr.arpa. for IP address 192.168.1.107 is not managed by this server

The correct reverse zone would be 1.168.192.in-addr.arpa., which exists.

The culprit lies in ipapython.dnsutil.zone_for_name respectively in the DNSResvoler implementation according to some preliminary debugging.

Version/Release/Distribution

4.9.0

@carbenium are you going to work on this?

@abbra Sorry, I won't have any time to spare for this in the next 1-2 weeks. Would be great if you could take over.

I have a backlog myself ;)

Ok, this is then free for take by anyone. :)

Metadata Update from @abbra:
- Issue priority set to: normal
- Issue set to the milestone: FreeIPA 4.9
- Issue tagged with: community

Well, I'd say this was a glitch in the matrix. Can't reproduce it anymore...

Metadata Update from @carbenium:
- Issue close_status updated to: worksforme
- Issue status updated to: Closed (was: Open)

I've seen this before, a lot, while testing ansible-freeipa's ipadnsrecord module.

The annoying part is that it is intermittent, and I did not found a way to reproduce it more consistently.
Metadata
None

community

None
None
Normal
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.