On 24/04/2019 09:46, Lester Caine wrote:This is another area where it can be a full time job and CURRENTLY I'm looking at domains registered across several registrars on several different DNS server systems so AM trying to decide how to streamline that. Some specialist DNS service providers will do round robin for you but I've not looked into their services in detail. I don't know what sort or heartbeat checking they might or might not be able to provide. If it was me in this scenario, I'd set up my own authoritative DNS server (or servers if I wanted one for each line, which would be preferable) and then tell the registrars to point to my DNS servers for DNS resolution for the domains in question. Any competent registrar should be able to do this nowadays. Thus you can keep the domains registered at whatever registrars were used. It's just the DNS that you're taking over. In an ideal world a nice PHP powered management tool to handle DNS settings, certificate renewals and all the other infrastructure would be nice? Just keeping certbot running at all is painful enough but adding local DNS may well be a necessary step Once you have things set up in a very basic way, it seems to me that writing a script to do these things would not be too difficult. I think the important thing would be to do it iteratively, a little bit at a time, incrementally adding features and links to subsystems. Just remember to document it well. :-) Perhaps it is time to simply scrap doing anything locally and just pay through the nose for someone else to deal with it all? And just get back to content. Nah, that would be too easy. As long as dual broadband lines give you enough outbound bandwidth, then I say stick with doing it yourself. -- Mark Rousell |
