Changing domain for backup svn server...

About 2 years ago I have created an SVN a setup where the production server runs VisualSvn 3.7 (using svn 1.9.7 I believe) on Windows Server 16.

For backup I have set up another svn server on an Ubuntu Server 18 LTS and I am using svnsync nightly to replicate all changes from the production server to the backup.

This backup server sits in my home with a 250/100 fiber connection to the Internet so it is plenty fast even though very far away from the production server.

As the svnsync is done over the Internet I have opened the SSL port on the backup server's network router and pointed it towards the Ubuntu server. On the production system I have used a dynamic dns domain to point to the backup system.

This has worked fine but there are two issues I am not happy about:

1) The dynamic domain name starts with "home", which is what I already had. But I think I would rather have a svn.mydomain.com type address..
So I have created it and also set up a refresh of its address on the actual backup server so it points to the same address as "home" does.

Question 1:
-----------
What do I need to do on the production server to let svnsync use the new domain address? Note that it will reach the exact same entry point on the backup server as it does now so the unique ID:s of the svn repositories will nbot be affected. But I guess since the URL will be a bit different something needs to be fixed...
Is there something special to handle?

2) The backup server installation uses a self-signed ssl certificate...
My backup server was set up when I did not know I could get a signed certificate via Certbot and now I don't really know how to change it into a signed cert. When I set up svn on Ubuntu I just followed the steps and in that chain there was a cert generation followed by self-signing it.

Question 2:
-----------
What would be my best approach to change the cert to a certbot provided self-signed one?
Will the cert change affect the above mentioned svnsync process?

---
Bo Berglund