How could I redirect in bind to another host in case server 1 went down?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have two servers with same service, so
server 1 xxx.myhost.com A record ip 1.1.1.1
server 2 xx2.myhost.com CNAME record to otherhost.com
The server number 1 is the principal, so, I gave to my clients this host (xxx.myhost.com) to get access.
Server 2 is a supporting server, in case #1 is not working.
I want to know: supposing server 1 went down for any reason,
how should I configure bind to redirect to server 2?
so graphically my client call xxx.myhost.com ----it's down--- so bind automatically redirect to----xx2.myhost.com.
And of course my clients don't know about server 2 and they don't need to know it...
It's like MX servers ...only with A and CNAME records....
Sorry for my bad English.
dns redirection forwarding bind
edited Jul 24 '14 at 20:01
Scott
16.2k113990
asked Jul 24 '14 at 19:03
PablossPabloss
62
add a comment |
I have two servers with same service, so
server 1 xxx.myhost.com A record ip 1.1.1.1
server 2 xx2.myhost.com CNAME record to otherhost.com
The server number 1 is the principal, so, I gave to my clients this host (xxx.myhost.com) to get access.
Server 2 is a supporting server, in case #1 is not working.
I want to know: supposing server 1 went down for any reason,
how should I configure bind to redirect to server 2?
so graphically my client call xxx.myhost.com ----it's down--- so bind automatically redirect to----xx2.myhost.com.
And of course my clients don't know about server 2 and they don't need to know it...
It's like MX servers ...only with A and CNAME records....
Sorry for my bad English.
dns redirection forwarding bind
edited Jul 24 '14 at 20:01
Scott
16.2k113990
asked Jul 24 '14 at 19:03
PablossPabloss
62
add a comment |
I have two servers with same service, so
server 1 xxx.myhost.com A record ip 1.1.1.1
server 2 xx2.myhost.com CNAME record to otherhost.com
The server number 1 is the principal, so, I gave to my clients this host (xxx.myhost.com) to get access.
Server 2 is a supporting server, in case #1 is not working.
I want to know: supposing server 1 went down for any reason,
how should I configure bind to redirect to server 2?
so graphically my client call xxx.myhost.com ----it's down--- so bind automatically redirect to----xx2.myhost.com.
And of course my clients don't know about server 2 and they don't need to know it...
It's like MX servers ...only with A and CNAME records....
Sorry for my bad English.
dns redirection forwarding bind
edited Jul 24 '14 at 20:01
Scott
16.2k113990
asked Jul 24 '14 at 19:03
PablossPabloss
62
I have two servers with same service, so
server 1 xxx.myhost.com A record ip 1.1.1.1
server 2 xx2.myhost.com CNAME record to otherhost.com
The server number 1 is the principal, so, I gave to my clients this host (xxx.myhost.com) to get access.
Server 2 is a supporting server, in case #1 is not working.
I want to know: supposing server 1 went down for any reason,
how should I configure bind to redirect to server 2?
so graphically my client call xxx.myhost.com ----it's down--- so bind automatically redirect to----xx2.myhost.com.
And of course my clients don't know about server 2 and they don't need to know it...
It's like MX servers ...only with A and CNAME records....
Sorry for my bad English.
dns redirection forwarding bind
dns redirection forwarding bind
edited Jul 24 '14 at 20:01
Scott
16.2k113990
asked Jul 24 '14 at 19:03
PablossPabloss
62
edited Jul 24 '14 at 20:01
Scott
16.2k113990
asked Jul 24 '14 at 19:03
PablossPabloss
62
edited Jul 24 '14 at 20:01
Scott
16.2k113990
edited Jul 24 '14 at 20:01
Scott
16.2k113990
edited Jul 24 '14 at 20:01
Scott
16.2k113990
16.2k113990
asked Jul 24 '14 at 19:03
PablossPabloss
62
asked Jul 24 '14 at 19:03
PablossPabloss
62
asked Jul 24 '14 at 19:03
PablossPabloss
62
62
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
What you're looking for is failover. This has actually been covered more technically over on ServerFault. But the tl;dr version is that Bind has no native facility for this.
You could use DDNS and zone updates to achieve this, but that would require quite a bit of additional configuration.
I guess you could also set up a custom script to monitor the server and push a zone update when it goes down. But again, quite a bit of custom configuration there. And it would be subject to the same problems mentioned in the first link - namely DNS caching.
As Rex said in the first link, some DNS providers, such as Route53 (which I have personal experience with) have integrated failover capability. This is probably the most 'sane' implementation.
A more exotic option is to set up the DNS to point to a 'gateway' server, which has static routes pointing to the 'preferred' server. A daemon of some type can check if the server is alive and change the routes as needed. This wouldn't have DNS latency, but - again - this is a pretty custom setup.
Links:
- https://serverfault.com/questions/495124/a-record-failover
- http://www.linux-faqs.info/dns/failover-dynamic-dns-bind-and-dhcp
answered Jul 24 '14 at 22:23
ChrisChris
480415
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f787637%2fhow-could-i-redirect-in-bind-to-another-host-in-case-server-1-went-down%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
What you're looking for is failover. This has actually been covered more technically over on ServerFault. But the tl;dr version is that Bind has no native facility for this.
You could use DDNS and zone updates to achieve this, but that would require quite a bit of additional configuration.
I guess you could also set up a custom script to monitor the server and push a zone update when it goes down. But again, quite a bit of custom configuration there. And it would be subject to the same problems mentioned in the first link - namely DNS caching.
As Rex said in the first link, some DNS providers, such as Route53 (which I have personal experience with) have integrated failover capability. This is probably the most 'sane' implementation.
A more exotic option is to set up the DNS to point to a 'gateway' server, which has static routes pointing to the 'preferred' server. A daemon of some type can check if the server is alive and change the routes as needed. This wouldn't have DNS latency, but - again - this is a pretty custom setup.
Links:
- https://serverfault.com/questions/495124/a-record-failover
- http://www.linux-faqs.info/dns/failover-dynamic-dns-bind-and-dhcp
answered Jul 24 '14 at 22:23
ChrisChris
480415
add a comment |
What you're looking for is failover. This has actually been covered more technically over on ServerFault. But the tl;dr version is that Bind has no native facility for this.
You could use DDNS and zone updates to achieve this, but that would require quite a bit of additional configuration.
I guess you could also set up a custom script to monitor the server and push a zone update when it goes down. But again, quite a bit of custom configuration there. And it would be subject to the same problems mentioned in the first link - namely DNS caching.
As Rex said in the first link, some DNS providers, such as Route53 (which I have personal experience with) have integrated failover capability. This is probably the most 'sane' implementation.
A more exotic option is to set up the DNS to point to a 'gateway' server, which has static routes pointing to the 'preferred' server. A daemon of some type can check if the server is alive and change the routes as needed. This wouldn't have DNS latency, but - again - this is a pretty custom setup.
Links:
- https://serverfault.com/questions/495124/a-record-failover
- http://www.linux-faqs.info/dns/failover-dynamic-dns-bind-and-dhcp
answered Jul 24 '14 at 22:23
ChrisChris
480415
add a comment |
What you're looking for is failover. This has actually been covered more technically over on ServerFault. But the tl;dr version is that Bind has no native facility for this.
You could use DDNS and zone updates to achieve this, but that would require quite a bit of additional configuration.
I guess you could also set up a custom script to monitor the server and push a zone update when it goes down. But again, quite a bit of custom configuration there. And it would be subject to the same problems mentioned in the first link - namely DNS caching.
As Rex said in the first link, some DNS providers, such as Route53 (which I have personal experience with) have integrated failover capability. This is probably the most 'sane' implementation.
A more exotic option is to set up the DNS to point to a 'gateway' server, which has static routes pointing to the 'preferred' server. A daemon of some type can check if the server is alive and change the routes as needed. This wouldn't have DNS latency, but - again - this is a pretty custom setup.
Links:
- https://serverfault.com/questions/495124/a-record-failover
- http://www.linux-faqs.info/dns/failover-dynamic-dns-bind-and-dhcp
answered Jul 24 '14 at 22:23
ChrisChris
480415
What you're looking for is failover. This has actually been covered more technically over on ServerFault. But the tl;dr version is that Bind has no native facility for this.
You could use DDNS and zone updates to achieve this, but that would require quite a bit of additional configuration.
I guess you could also set up a custom script to monitor the server and push a zone update when it goes down. But again, quite a bit of custom configuration there. And it would be subject to the same problems mentioned in the first link - namely DNS caching.
As Rex said in the first link, some DNS providers, such as Route53 (which I have personal experience with) have integrated failover capability. This is probably the most 'sane' implementation.
A more exotic option is to set up the DNS to point to a 'gateway' server, which has static routes pointing to the 'preferred' server. A daemon of some type can check if the server is alive and change the routes as needed. This wouldn't have DNS latency, but - again - this is a pretty custom setup.
Links:
- https://serverfault.com/questions/495124/a-record-failover
- http://www.linux-faqs.info/dns/failover-dynamic-dns-bind-and-dhcp
answered Jul 24 '14 at 22:23
ChrisChris
480415
answered Jul 24 '14 at 22:23
ChrisChris
480415
answered Jul 24 '14 at 22:23
ChrisChris
480415
answered Jul 24 '14 at 22:23
ChrisChris
480415
480415
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f787637%2fhow-could-i-redirect-in-bind-to-another-host-in-case-server-1-went-down%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
