Hi guys,
I am having some problems setting the dns records for virtual servers (for my home server with a dynamic ip) in Virtualmin (and yes, I am a newbie :D). But first, read my story please :
Google Settings :
I have a domain registered on google domains, let's say : example.com . I have set up, in google domains, from synthetic records a dynamic dns called site.example.com .
Asus Router Settings :
In my asus router from WAN -> DDNS, i have setup using the server : domains.google.com, the host name site.example.com with the credentials google provided. All is set and working. If I ping site.example.com it will get me the right ip from home.
Server Settings:
I have a Centos 7-5.1804 server that connects to my router and has the fix ip 192.168.1.44 and I can access my server from outside (all required ports are forwarded from my router ) .
Virtualmin Settings
I have installed and configured Virtualmin (with the hostname site.example.com ) and created a new virtual server named test1.site.example.com . How do I setup the virtual server or Virtualmin so I can see test1.site.example.com from outside. Its this possible?
Thanks a lot guys !
From what I have looked, its kinda impossible to make it work with a ddns,
Dynanmic dns means you subscribe to a dynamic dns service that handles the updating of your IP. . It does not mean virtualmin will update your domain name at a registrar like google.
Use DDclient
Where is your web hosting server, at home/office, or in a datacenter?
If it's in your home office and you aren't setup with your ISP for a static IP address, why don't you just pay for a static ipaddress (it's really not expensive to get one in most countries...for example I pay the equivalent of $7 US /month for mine. Most spend more than that on coffee each day)
I would imagine, if at least your name servers had a static IP address, you could run a cron within virtualmin to regularly check for and if changed obtain the new public ipaddress and then use that to update virtualmin bind dns records on your namesevers. Propogation is a bit of a pain, ttl would have to be set ridiculously low to even attempt to maintain some kind of stable connection...and probably you would have to use caching. In the end, static IP is going to be a lot more reliable, less hassle, and cheaper.
In my view, ddns isn't reliable...just look how often mobile phone calls get disconnected when changing towers and when phone ipaddress changes. It's terrible. Whilst still doable,generally we have enough troubles...and adding this to the equation would be hopeless for web server without a lot of workarounds to overcome this issue.
Anyway, if you must go down this pathway, as mentioned us DDCLIENT or INADYN.
Google have a good article on setting it up to work with their servers...
https://support.google.com/domains/answer/6147083?hl=en
https://ajecreative.com.au