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

Good afternoon, Mr. Principi,
since Upgrade NS7 >> NS8 we could work with the “wrong” user domain directory.nh … only some little problems…
But since update on beginning of may we have an annoying problem in nextcloud / file share https://community.nethserver.org/t/nextcloud-cant-create-share/25796
We think directory.nh is the reason.
Is there any way to change from directory.nh to firma.lan on the running system?
Sadly I don’t understand what to do … Hope you can help .

I don’t know if newer Nextcloud versions have changed their expectations towards the LDAP suffix. I don’t think so.

If your DB comes from NS7, you can now manually set the mail field from the Domain and Users page. I hope it helps.

1 Like

Thanks,
but this is not the problem…
The problem is:
Since beginning of may it is not possible to share a document INSIDE the user domain, without using email. At example user01 share a document direct with user09…
There is a chaos in domain directory.nh - see what I mean:


We want to solve this chaos, because it could be a reason of trouble in the future.
We wish to create a clean system - but how we can do that

I tried to reproduce the issue but without success.
After migrating Nextcloud and OpenLDAP to NS8 using the domain “directory.nh”, I’m still able to share files among users, using the old domain name.

1 Like