#2952 Incorrect suggested Zone name when using name-from-ip
Closed: Invalid None Opened 11 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=842756 (Red Hat Enterprise Linux 6)

Description of problem:
When adding a reverse zone using name-from-ip, the prompt suggests an invalid
zone name, using all 4 octets of the ip.

Version-Release number of selected component (if applicable):
freeipa-server-2.99.0-0.20120713T1418Zgitc20d4c7.fc17.x86_64

How reproducible:
always

Steps to Reproduce:
1.# ipa dnszone-add --name-from-ip=10.15.20.100
--name-server=qe-blade-04.testrelm.com
2. ]# ipa dnszone-add --name-from-ip=10.15.20
--name-server=qe-blade-04.testrelm.com


Actual results:
1. Step 1 prompts: Zone name [100.20.15.10.in-addr.arpa.]:
2. Step 2 prompts: Zone name [0.20.15.10.in-addr.arpa.]:

Expected results:
Step 1: Prompt should be:
Zone name [20.15.10.in-addr.arpa.]:
Step 2: should be Validation Error - to indicate invalid ip

Additional info:

Summary from discussion in Bugzilla - DNS zone with all IP address components is ok, we just want to improve default IP network mask computation to be rather based on IP address class instead of fixed value (32b for IPv4 and 128b for IPv6).

Moving my tickets back to free-to-take pool.

See https://bugzilla.redhat.com/show_bug.cgi?id=842756#c3. The suggested improvement was already done in current FreeIPA/IdM (tested on 4.1):

# ipa dnszone-add --name-from-ip=10.0.0.1
Zone name [0.0.10.in-addr.arpa.]: ^C

It now uses a better suited default and does not use the full 32b network mask. Closing the bug.

Metadata Update from @mkosek:
- Issue assigned to someone
- Issue set to the milestone: Future Releases

7 years ago

Login to comment on this ticket.

Metadata