When creating an Internal OpenLDAP Domain, the domain validation fails when the domain or sub-domain starts with one or more numbers. Validation is successful only when starting with [a-zA-Z].
From the second screenshot, I performed a search (find / -name “configure-module”) on the server and found the directory /home/openldap3/.config/actions/configure-module.
In the directory, I updated the domain name validation pattern in the file validate-input.json as follows:
Before : ^[a-zA-Z][-a-zA-Z0-9]{0,62}(\.[a-zA-Z][-a-zA-Z0-9]{0,62})+$
After : ^[a-zA-Z0-9][-a-zA-Z0-9]{0,62}(\.[a-zA-Z][-a-zA-Z0-9]{0,62})+$
After updating the pattern, the Internal OpenLDAP domain validation succeeded and the domain was created.
2 Likes
Hi Dominic, I’ve nothing contrary but we must check if Active Directory accepts your change proposal 
I never tried, but it seems AD rules for the domain name are the same of DNS domain names, so a leading number is allowed.
I filed a card (NethServer 8 · GitHub) but I’d like to know if anybody as ever deployed an AD domain name with a leading number, like 1st-ad.example.org.
For OpenLDAP there shouldn’t be any issue, but I’d like to fix also AD…