Hi All
I've a client that had not updated their on premise V16 system and started to have problems with emailing from 3cx smtp with 5.7.0 errors due to changes with the 3cx background servers, as documented.
Checking the forum lead them to update to v18, they had the option available as this was an ISO build, this is a debian install.
Prior to the update the FQDN of the system was registered and responding to lookups.
After the upgrade the client refreshed the licence and the system is working ok, however the FQDN has become deregistered and is not shown on the clients customer portal as associated to either the v16 or v18 licence.
They have tried the process of changing IP from static to dynamic and back again but no joy.
There seem to be recent similar threads following v16>v18 upgrades
https://www.3cx.com/community/threads/dns-record-not-valid.116097/#post-537902
Are there any other options than a new install?
Thanks in advance
I've a client that had not updated their on premise V16 system and started to have problems with emailing from 3cx smtp with 5.7.0 errors due to changes with the 3cx background servers, as documented.
Checking the forum lead them to update to v18, they had the option available as this was an ISO build, this is a debian install.
Prior to the update the FQDN of the system was registered and responding to lookups.
After the upgrade the client refreshed the licence and the system is working ok, however the FQDN has become deregistered and is not shown on the clients customer portal as associated to either the v16 or v18 licence.
They have tried the process of changing IP from static to dynamic and back again but no joy.
There seem to be recent similar threads following v16>v18 upgrades
https://www.3cx.com/community/threads/dns-record-not-valid.116097/#post-537902
Are there any other options than a new install?
Thanks in advance
