I use a professional server from home and I have Duck DNS which, together with a script, updates any IP change without problems. Today, for some strange reason, virtualmin continues to indicate the old public IP and does not detect that it has already changed, which has forced me to manually change the DNS of all the domains.
I have tried several times and leaving a time of more than 10 seconds after turning off:
Restart the server.
Restart router.
Restart switch.
It still hasn’t detected that the public IP changed: 192.168.1.NNN:NNNN/virtual-server/edit_newdynip.cgi?xnavigation=1
I think webmin uses dynip.pl to keep what I’m saying up to date… I’m still studying the matter… Is the service operational? Any ideas?
PD: I speak Spanish and my English can be greatly improved. Excuse me.
I don’t know that Webmin/Virtualmin support dynamic DNS. I worked for a company that used a private ip address scheme internally and then mapped them to an external public IP. You may need to do something similar.
Virtualmin does accept dynamic DNS. In my main message of this entry I left a link to where it is located.
Additionally, without doing anything, today I received the notice that virtualmin detected the public IP change, but after many hours. It is an anomaly that has never happened before. I suspect that virtualmin/webmin have some external service to check if I change the public IP to trigger the actions indicated in the virtual-server/edit_newdynip.cgi?xnavigation=1 section …but I still did not have time to investigate further.
I’m marking on the calendar when it happens and how long it takes to detect the change. In addition to implementing some “improvements”; optimize DNS server, own script in parallel to the virtualmin functionality, etc.