And a slave server in the cloud can be set up to track the in house masters automatically via zone transfers, you would never need to touch the configuration except to add or delete a whole forward or reverse domain, like if you acquired additional IP blocks.
Easy enough to do on a rented VM, or you could arrange with another ISP to be backups for each other. From: AF <[email protected]> On Behalf Of Mark - Myakka Technologies Sent: Monday, July 29, 2019 12:36 PM To: AnimalFarm Microwave Users Group <[email protected]> Subject: Re: [AFMUG] Reverse DNS Hosting Josh, I do a primary server in house and secondary in cloud. -- Best regards, Mark <mailto:[email protected]> mailto:[email protected] Myakka Technologies, Inc. <http://www.Myakka.com> www.Myakka.com ------ Monday, July 29, 2019, 1:25:02 PM, you wrote: We host primary and secondary authoritative DNS in house, but also have a tertiary host in AWS that runs BIND as well. Josh On Mon, Jul 29, 2019 at 1:23 PM Matt < <mailto:[email protected]> [email protected]> wrote: Currently use a Centos 7 VM running bind to internally host our forward and reverse DNS records. After a cut in fiber that this rode on few months back I am thinking it would be better to out source this. Plus, I just want less boxes to update. What is everyone else using for DNS hosting that supports pointer records? -- AF mailing list <mailto:[email protected]> [email protected] <http://af.afmug.com/mailman/listinfo/af_af.afmug.com> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
-- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
