should not
this is defently a problem in your network config /dns config with the new subnet
zimbra itself doesnt care which ip is to use -
but (which isnt optimal) it needs defently a correct dns and /etc/hosts entrys
otherwise your services will stop and never come back
so really check dns
easist is ping on the zimbrahost the hostname like
ping zimbra.example.net
then ping it outside - see if you get a request / ips matching
maybe you forgot to update your filewall script?
does any other service work well wit the new subnet? |