Missunderstand directory.nh

NethServer Version: 8
Module: mail migration
On server NS7 our user domain was firma.lan … (LDAP)
and our mail domains were firma.lan and alias FIRMA.DE
But migration forced us to use directory.nh - wihout this no go.
Now we have user domain directory.nh and in mail 2 domains

firma.lan and firma.de

Is there a misunderstanding or is better say: is it possible to “repair” ?

It is not possible to rename a LDAP domain without rewriting the whole LDAP DB with some custom script.

A planned improvement is to allow the migration of many NS7 to the same NS8 cluster, and also fix a migration problem if the LDAP comes from a previous NS6 migration.

See also:

2 Likes

Since the release of Core 3.3.0 and migration tool 1.1.0 it is possible to assign a domain name (and LDAP suffix) at the beginning of the migration procedure.

More information NethServer 7 migration — NS8 documentation

Thanks to @stephdl, @giacomo, @Amygos for their hard work!

4 Likes

… very nice…
But what should we do …?
We migrated NS7 > NS8 at 06.September and “misunderstood directory.nh”
Now our user domain is directory.nh, because xyz.lan was not possible.
Is it possible to correct ? if yes: how ?
P.S. NS8 goes on debian12 as a VM on Proxmox → restore needs 2,5 hours
Greetings !

not possible for now and I am not sure it will be a day due to many problems that you could find. Saying that my migration script should work but of course it must be done manually on your side

But the domain of LDAP is not really interesting, you can live with directory.nh because it is not used to authenticate mail users for example

…except that it’s used as the domain for the postmaster when it sends delivery failure messages–they come from mailer-daemon@directory.nh.

2 Likes

Thanks to you,
now we are rest assured

Have a good New Year!

1 Like