Is it possible to request custom nameservers with BudgetVM, or will we have to configure that ourselves? The former would be so much more ideal for a plethora of reasons (namely, not consuming 2 of my 3 IPs, not to mention the ease of deployment).
[I currently have an open ticket with them asking a very similar, non-redacted version of this post. But, I'd love to hear the community's feedback, too!]
Seeing how our cPanel server will be authoritative for the DNS; can I simply create A records for ns1/ns2.mydomain.com and point them at two of our respective IPs? Of course, I will have to update my information with our registrar, as well.
Is there an up-to-date article / tutorial that I've overlooked, or could you point us in the right direction? I've spent hours searching threads and the web, but the articles are fairly dated (not that the RFC has changed much in the last few years)...
In the past, depending on the timeframe, I had either been using a reseller account with custom nameservers provided, and even prior to that I've used PDNS with dedicated, redundant Master-Slave DNS servers. The PDNS cluster was fairly straight forward, but it was also pre-configured prior to my arrival. And, since I'm no longer working with that organization and have just recently started to branch out on my own, I can hardly justify the cost of 4 additional VPS' to handle DNS at such a small scale.
The best part is, once we get this worked out... I still have to implement HA. But, first and foremost, I need to get the initial server setup. Fun times!
With that being said, assuming 1) that BudgetVM doesn't provide white-labled nameservers, and 2) that we can take two of our allocated IPs and setup A records for NS1/NS2.mydomain.com to point to our [northern] cPanel host; in theory, when we deploy into the [southern] DC, I will be able to use two of those IPs to create NS3/NS4 records and point to the [southern] cPanel host, correct?
The ideal goal is to use AWS' Route53 to perform weighted round robin DNS and have two geographically separate hosts providing the same content at all times.
That is what we're shooting for, at least. If I can't run hot-hot, then hot-cold failover will be tolerable until I get the rest of our infrastructure in place. Honestly, the hot-hot configuration will be a first for me, whereas, at least I know how to implement the latter (hot-cold) configuration.
Unfortunately, BIND has always been my biggest 'gotchya'. I like to think I have a solid understanding of DNS, but it really is one of my least favorite parts of the job. Honestly.
I'm fairly certain that I can create the new A records for NS1/NS2 and point them to the cPanel's IP and that they will resolve. The biggest hurdle I foresee is getting the DNS records to propagate from one DC to the other. So, say for example, if an admin logins to the DC1 host and manually creates a new account, that DNS will not immediately be available to the DC2 host until rysnc runs. I'm not sure how I'm going to tackle that issue... Esepcially without having a dedicated Master-Slave DNS configuration (in which case axfr would be the "easy" solution). But, one thing at a time, as they say. Although, I'd much rather have a clear road-map going forward now instead of trying to figure out these "details" when the time comes.
If nothing else, I'm willing to utilize a 3rd party for the DNS in the meantime until we can afford to deploy a Master-Slave DNS configuration, and justify the cost to do so.
Now, with all of that being said, I understand that I've covered a wide-breadth of topics here, and the last half is hardly for the squeamish. But, as a web developer turned Sys Admin, I'm looking forward to this endeavor, honestly.
I look forward to your advice and insight. And, thank you for your time and assistance.