Authoritative DNS Migration Question












0















I have 3 DNS servers, two existing, one new:



DNS (P): abc.xyz (1.1.1.1)     - Primary
DNS (S): a.abc.xyz (1.1.1.2) - Secondary. Authoritative for a.abc.xyz, b.zbc.xyz, c.zbc.xyz.

DNS (M): a.abc.xyz (1.1.1.3) - Migrated: New Secondary.


I need to migrate DNS (S) to DNS (M) in such a way as not to incur downtime on VM's dependent on "DNS (S)" .



Tried to add "DNS (M)" to the list of forwarders on "DNS (S)" but that did not work and entries still resolved on "DNS (S)" . Used "forward only". ( DNS forward only )



What would be the best approach to do this sort of migration without incurring downtime on the VM's dependent on "DNS (S)" ? I'm hoping for a gradual migration so we have time to eventually migrate all VM's to the new DNS then cut over all delegated domains over to the new one.



Or perhaps I could reconfigure the "DNS (D)" pair for a cluster, adjust the delegation on "DNS (P)" for new IP's then shut down "DNS (S)" ?



Option I would prefer not to use is a big bang approach where we 'hope' to forward everything in one shot expecting not to miss anything using the "DNS (S)" servers. ( Something always goes wrong in such an approach for hundreds of VM's. )



Cheers,










share|improve this question


















  • 1





    Is any part of this a UNIX/Linux question?

    – Jeff Schaller
    2 hours ago
















0















I have 3 DNS servers, two existing, one new:



DNS (P): abc.xyz (1.1.1.1)     - Primary
DNS (S): a.abc.xyz (1.1.1.2) - Secondary. Authoritative for a.abc.xyz, b.zbc.xyz, c.zbc.xyz.

DNS (M): a.abc.xyz (1.1.1.3) - Migrated: New Secondary.


I need to migrate DNS (S) to DNS (M) in such a way as not to incur downtime on VM's dependent on "DNS (S)" .



Tried to add "DNS (M)" to the list of forwarders on "DNS (S)" but that did not work and entries still resolved on "DNS (S)" . Used "forward only". ( DNS forward only )



What would be the best approach to do this sort of migration without incurring downtime on the VM's dependent on "DNS (S)" ? I'm hoping for a gradual migration so we have time to eventually migrate all VM's to the new DNS then cut over all delegated domains over to the new one.



Or perhaps I could reconfigure the "DNS (D)" pair for a cluster, adjust the delegation on "DNS (P)" for new IP's then shut down "DNS (S)" ?



Option I would prefer not to use is a big bang approach where we 'hope' to forward everything in one shot expecting not to miss anything using the "DNS (S)" servers. ( Something always goes wrong in such an approach for hundreds of VM's. )



Cheers,










share|improve this question


















  • 1





    Is any part of this a UNIX/Linux question?

    – Jeff Schaller
    2 hours ago














0












0








0








I have 3 DNS servers, two existing, one new:



DNS (P): abc.xyz (1.1.1.1)     - Primary
DNS (S): a.abc.xyz (1.1.1.2) - Secondary. Authoritative for a.abc.xyz, b.zbc.xyz, c.zbc.xyz.

DNS (M): a.abc.xyz (1.1.1.3) - Migrated: New Secondary.


I need to migrate DNS (S) to DNS (M) in such a way as not to incur downtime on VM's dependent on "DNS (S)" .



Tried to add "DNS (M)" to the list of forwarders on "DNS (S)" but that did not work and entries still resolved on "DNS (S)" . Used "forward only". ( DNS forward only )



What would be the best approach to do this sort of migration without incurring downtime on the VM's dependent on "DNS (S)" ? I'm hoping for a gradual migration so we have time to eventually migrate all VM's to the new DNS then cut over all delegated domains over to the new one.



Or perhaps I could reconfigure the "DNS (D)" pair for a cluster, adjust the delegation on "DNS (P)" for new IP's then shut down "DNS (S)" ?



Option I would prefer not to use is a big bang approach where we 'hope' to forward everything in one shot expecting not to miss anything using the "DNS (S)" servers. ( Something always goes wrong in such an approach for hundreds of VM's. )



Cheers,










share|improve this question














I have 3 DNS servers, two existing, one new:



DNS (P): abc.xyz (1.1.1.1)     - Primary
DNS (S): a.abc.xyz (1.1.1.2) - Secondary. Authoritative for a.abc.xyz, b.zbc.xyz, c.zbc.xyz.

DNS (M): a.abc.xyz (1.1.1.3) - Migrated: New Secondary.


I need to migrate DNS (S) to DNS (M) in such a way as not to incur downtime on VM's dependent on "DNS (S)" .



Tried to add "DNS (M)" to the list of forwarders on "DNS (S)" but that did not work and entries still resolved on "DNS (S)" . Used "forward only". ( DNS forward only )



What would be the best approach to do this sort of migration without incurring downtime on the VM's dependent on "DNS (S)" ? I'm hoping for a gradual migration so we have time to eventually migrate all VM's to the new DNS then cut over all delegated domains over to the new one.



Or perhaps I could reconfigure the "DNS (D)" pair for a cluster, adjust the delegation on "DNS (P)" for new IP's then shut down "DNS (S)" ?



Option I would prefer not to use is a big bang approach where we 'hope' to forward everything in one shot expecting not to miss anything using the "DNS (S)" servers. ( Something always goes wrong in such an approach for hundreds of VM's. )



Cheers,







dns migration






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 4 hours ago









DigitalTidBitsDigitalTidBits

163




163








  • 1





    Is any part of this a UNIX/Linux question?

    – Jeff Schaller
    2 hours ago














  • 1





    Is any part of this a UNIX/Linux question?

    – Jeff Schaller
    2 hours ago








1




1





Is any part of this a UNIX/Linux question?

– Jeff Schaller
2 hours ago





Is any part of this a UNIX/Linux question?

– Jeff Schaller
2 hours ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503008%2fauthoritative-dns-migration-question%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503008%2fauthoritative-dns-migration-question%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Loup dans la culture

How to solve the problem of ntp “Unable to contact time server” from KDE?

ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux