1) Sign into your node
2) Sign into your domain registrar and update your record with the updated host name
3) Update the FQDN variable
FQDN='FQDN'
Note: you will need to type this command and change 'FQDN' (the value between the quotes ' ') to the value used in the domain registration for your node
4) Update the .bashrc file with the new FQDN
echo "export FQDN=$FQDN" >> $HOME/.bashrc
5) Update your zen.conf by manually editing it with nano
nano ~/.zen/zen.conf
Arrow down to the two lines: tlscertpath and tlskeypath and delete and replace the existing FQDN cert path with your updated FQDN
Save and exit with CTRL+X, type y and hit <enter>
6) Verify your FQDN has fully propagated using: https://www.whatsmydns.net/
Note: Do not proceed until your FQDN has propagated fully
7) Delete the /etc/letsencrypt directory
sudo rm -rd /etc/letsencrypt
8) Re-Issue certificates for your new FQDN and update the certificate trusted store and apply proper file permissions
sudo certbot certonly -n --agree-tos --register-unsafely-without-email --standalone -d $FQDN
sudo cp /etc/letsencrypt/live/$FQDN/chain.pem /usr/local/share/ca-certificates/chain.crt
sudo update-ca-certificates
sudo chown -R root:sudo /etc/letsencrypt/
sudo chmod -R 750 /etc/letsencrypt/
9) Restart zend
sudo systemctl restart zend
10) Check that zend sees a valid TLS certificate (tls_cert_verified": true)
zen-cli getnetworkinfo | grep tls
11) Update the nodetracker configuration
cd ~/nodetracker && node setup.js
When prompted to enter your FQDN, enter the new one and <enter> through all other unchanged fields
12) Restart the tracker and check that the log output is as expected
sudo systemctl restart zentracker && journalctl -fu zentracker
13) Check on the tracker site to verify the new FQDN is in use and that there are no open exceptions
© 2020 Horizen. All rights reserved.