mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2025-02-25 18:55:28 -06:00
a001095856
Nameserver hostname passed to dnszone_add command was always treated as FQDN even though it was a relative DNS name to the new zone. All relative names were being rejected as unresolvable. Modify --name-server option processing in dnszone_add and dnszone_mod to respect FQDN/relative DNS name and do the checks accordingly. With this change, user can add a new zone "example.com" and let dnszone_add to create NS record "ns" in it, when supplied with its IP address. IP address check is more strict so that it is not entered when no forward record is created. Places misusing the option were fixed. Nameserver option now also accepts zone name, which means that NS and A record is placed to DNS zone itself. Also "@" is accepted as a nameserver name, BIND understand it also as a zone name. As a side-effect of this change, other records with hostname part (MX, KX, NS, SRV) accept "@" as valid hostname. BIND replaces it with respective zone name as well. Unit tests were updated to test the new format. https://fedorahosted.org/freeipa/ticket/3204
83 lines
4.0 KiB
Plaintext
83 lines
4.0 KiB
Plaintext
########################################################
|
|
# freeIPA Version #
|
|
# #
|
|
# freeIPA versions are as follows #
|
|
# 1.0.x New production series #
|
|
# 1.0.x{pre,rc}y Preview/Testing & RC #
|
|
# 1.0.0GITabcdefg Build from GIT #
|
|
# #
|
|
########################################################
|
|
|
|
########################################################
|
|
# This are the main version numbers #
|
|
# #
|
|
# <MAJOR>.<MINOR>.<RELEASE> #
|
|
# #
|
|
# e.g. IPA_VERSION_MAJOR=1 #
|
|
# IPA_VERSION_MINOR=0 #
|
|
# IPA_VERSION_RELEASE=0 #
|
|
# -> "1.0.0" #
|
|
########################################################
|
|
IPA_VERSION_MAJOR=3
|
|
IPA_VERSION_MINOR=0
|
|
IPA_VERSION_RELEASE=99
|
|
|
|
########################################################
|
|
# For 'pre' releases the version will be #
|
|
# #
|
|
# <MAJOR>.<MINOR>.<RELEASE>pre<PRE_RELEASE> #
|
|
# #
|
|
# e.g. IPA_VERSION_PRE_RELEASE=1 #
|
|
# -> "1.0.0pre1" #
|
|
########################################################
|
|
IPA_VERSION_PRE_RELEASE=
|
|
|
|
########################################################
|
|
# For 'rc' releases the version will be #
|
|
# #
|
|
# <MAJOR>.<MINOR>.<RELEASE>rc<RC_RELEASE> #
|
|
# #
|
|
# e.g. IPA_VERSION_RC_RELEASE=1 #
|
|
# -> "1.0.0rc1" #
|
|
########################################################
|
|
IPA_VERSION_RC_RELEASE=
|
|
|
|
########################################################
|
|
# To mark GIT snapshots this should be set to 'yes' #
|
|
# in the development BRANCH, and set to 'no' only in #
|
|
# the IPA_X_X_RELEASE BRANCH #
|
|
# #
|
|
# <MAJOR>.<MINOR>.<RELEASE>GITxxx #
|
|
# #
|
|
# e.g. IPA_VERSION_IS_SVN_SNAPSHOT=yes #
|
|
# -> "1.0.0GITabcdefg" #
|
|
########################################################
|
|
IPA_VERSION_IS_GIT_SNAPSHOT="yes"
|
|
|
|
########################################################
|
|
# The version of IPA data. This is used to identify #
|
|
# incompatibilities in data that could cause issues #
|
|
# with replication. If the built-in versions don't #
|
|
# match exactly then replication will fail. #
|
|
# #
|
|
# The format is %Y%m%d%H%M%S #
|
|
# #
|
|
# e.g. IPA_DATA_VERSION=`date +%Y%m%d%H%M%S` #
|
|
# -> "20100614120000" #
|
|
########################################################
|
|
IPA_DATA_VERSION=20100614120000
|
|
|
|
########################################################
|
|
# The version of the IPA API. This controls which #
|
|
# client versions can use the XML-RPC and json APIs #
|
|
# #
|
|
# A change to existing API requires a MAJOR version #
|
|
# update. The addition of new API bumps the MINOR #
|
|
# version. #
|
|
# #
|
|
# The format is a whole number #
|
|
# #
|
|
########################################################
|
|
IPA_API_VERSION_MAJOR=2
|
|
IPA_API_VERSION_MINOR=45
|