Could name server resolve IP address dynamically base on some strategy?
up vote
4
down vote
favorite
We have registered some name servers for DNS resolving for our website which is deployed in several data centers. Our current strategy of DNS resolve is that based on the different client IP addresses, the name server will return different IP addresses for the same domain. e.g, if the client IP address is from north America, the name server will return an IP address which is the IP address of our north America data center. But the client IP sometimes is not the real IP of the users. It may be an IP of DNS which belongs to ISP or a proxy server. On the other hand, if one of our data center is down, we want our name server exclude that IP address which belongs to the crashed data center. So we hope that we can get a more dynamic strategy for our DNS resolve. Is there any solution for that?
networking domain-name-system
edited 3 mins ago
Ron Maupin
2,0101512
asked 1 hour ago
yifan
211
New contributor
yifan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
4
down vote
favorite
We have registered some name servers for DNS resolving for our website which is deployed in several data centers. Our current strategy of DNS resolve is that based on the different client IP addresses, the name server will return different IP addresses for the same domain. e.g, if the client IP address is from north America, the name server will return an IP address which is the IP address of our north America data center. But the client IP sometimes is not the real IP of the users. It may be an IP of DNS which belongs to ISP or a proxy server. On the other hand, if one of our data center is down, we want our name server exclude that IP address which belongs to the crashed data center. So we hope that we can get a more dynamic strategy for our DNS resolve. Is there any solution for that?
networking domain-name-system
edited 3 mins ago
Ron Maupin
2,0101512
asked 1 hour ago
yifan
211
New contributor
yifan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This sounds like a case for anycast.
– Ron Maupin
1 hour ago
add a comment |
up vote
4
down vote
favorite
up vote
4
down vote
favorite
We have registered some name servers for DNS resolving for our website which is deployed in several data centers. Our current strategy of DNS resolve is that based on the different client IP addresses, the name server will return different IP addresses for the same domain. e.g, if the client IP address is from north America, the name server will return an IP address which is the IP address of our north America data center. But the client IP sometimes is not the real IP of the users. It may be an IP of DNS which belongs to ISP or a proxy server. On the other hand, if one of our data center is down, we want our name server exclude that IP address which belongs to the crashed data center. So we hope that we can get a more dynamic strategy for our DNS resolve. Is there any solution for that?
networking domain-name-system
edited 3 mins ago
Ron Maupin
2,0101512
asked 1 hour ago
yifan
211
New contributor
yifan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
We have registered some name servers for DNS resolving for our website which is deployed in several data centers. Our current strategy of DNS resolve is that based on the different client IP addresses, the name server will return different IP addresses for the same domain. e.g, if the client IP address is from north America, the name server will return an IP address which is the IP address of our north America data center. But the client IP sometimes is not the real IP of the users. It may be an IP of DNS which belongs to ISP or a proxy server. On the other hand, if one of our data center is down, we want our name server exclude that IP address which belongs to the crashed data center. So we hope that we can get a more dynamic strategy for our DNS resolve. Is there any solution for that?
networking domain-name-system
networking domain-name-system
edited 3 mins ago
Ron Maupin
2,0101512
asked 1 hour ago
yifan
211
New contributor
yifan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 3 mins ago
Ron Maupin
2,0101512
asked 1 hour ago
yifan
211
New contributor
yifan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 3 mins ago
Ron Maupin
2,0101512
edited 3 mins ago
Ron Maupin
2,0101512
edited 3 mins ago
Ron Maupin
2,0101512
2,0101512
asked 1 hour ago
yifan
211
New contributor
yifan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
yifan
211
asked 1 hour ago
yifan
211
211
New contributor
yifan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
yifan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
yifan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This sounds like a case for anycast.
– Ron Maupin
1 hour ago
add a comment |
This sounds like a case for anycast.
– Ron Maupin
1 hour ago
This sounds like a case for anycast.
– Ron Maupin
1 hour ago
This sounds like a case for anycast.
– Ron Maupin
1 hour ago
add a comment |
2 Answers
2
active
oldest
votes
up vote
2
down vote
It sounds like you want anycast. That is the type of thing that sites like Google use. You have a single address (resolved by DNS) for all your web sites, and you let the Internet routing protocol (BGP) direct the users to the nearest (by the routing protocol) site. If a site goes down, the next closest site is placed in the Internet routing table automatically by BGP.
The classic example is 8.8.8.8 for DNS. It resolves to different locations around the globe, and if one location goes down, then it goes to the next closest location.
The answer is not DNS, it is routing.
answered 51 mins ago
Ron Maupin
2,0101512
add a comment |
up vote
0
down vote
What you need is exactly what Amazon Route53 DNS service offers:
Latency based routing - Route end users to the AWS region that provides the lowest possible latency.
Geo DNS - Route end users to a particular endpoint that you specify based on the end user’s geographic location.
Health Checks and Failover - Amazon Route 53 can monitor the health and performance of your application as well as your web servers and other resources.
... and many more advanced DNS features.
You don't have to host your website on AWS to be able to use Route53, it will happily work with services deployed across private datacentres.
Unless you're a Facebook or Google pricing should be an issue either, starting from $0.40 per million requests (see pricing details).
Hope that helps :)
answered 6 mins ago
MLu
4,79011633
Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
– zypA13510
2 mins ago
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
It sounds like you want anycast. That is the type of thing that sites like Google use. You have a single address (resolved by DNS) for all your web sites, and you let the Internet routing protocol (BGP) direct the users to the nearest (by the routing protocol) site. If a site goes down, the next closest site is placed in the Internet routing table automatically by BGP.
The classic example is 8.8.8.8 for DNS. It resolves to different locations around the globe, and if one location goes down, then it goes to the next closest location.
The answer is not DNS, it is routing.
answered 51 mins ago
Ron Maupin
2,0101512
add a comment |
up vote
2
down vote
It sounds like you want anycast. That is the type of thing that sites like Google use. You have a single address (resolved by DNS) for all your web sites, and you let the Internet routing protocol (BGP) direct the users to the nearest (by the routing protocol) site. If a site goes down, the next closest site is placed in the Internet routing table automatically by BGP.
The classic example is 8.8.8.8 for DNS. It resolves to different locations around the globe, and if one location goes down, then it goes to the next closest location.
The answer is not DNS, it is routing.
answered 51 mins ago
Ron Maupin
2,0101512
add a comment |
up vote
2
down vote
up vote
2
down vote
It sounds like you want anycast. That is the type of thing that sites like Google use. You have a single address (resolved by DNS) for all your web sites, and you let the Internet routing protocol (BGP) direct the users to the nearest (by the routing protocol) site. If a site goes down, the next closest site is placed in the Internet routing table automatically by BGP.
The classic example is 8.8.8.8 for DNS. It resolves to different locations around the globe, and if one location goes down, then it goes to the next closest location.
The answer is not DNS, it is routing.
answered 51 mins ago
Ron Maupin
2,0101512
It sounds like you want anycast. That is the type of thing that sites like Google use. You have a single address (resolved by DNS) for all your web sites, and you let the Internet routing protocol (BGP) direct the users to the nearest (by the routing protocol) site. If a site goes down, the next closest site is placed in the Internet routing table automatically by BGP.
The classic example is 8.8.8.8 for DNS. It resolves to different locations around the globe, and if one location goes down, then it goes to the next closest location.
The answer is not DNS, it is routing.
answered 51 mins ago
Ron Maupin
2,0101512
answered 51 mins ago
Ron Maupin
2,0101512
answered 51 mins ago
Ron Maupin
2,0101512
answered 51 mins ago
Ron Maupin
2,0101512
2,0101512
add a comment |
add a comment |
up vote
0
down vote
What you need is exactly what Amazon Route53 DNS service offers:
Latency based routing - Route end users to the AWS region that provides the lowest possible latency.
Geo DNS - Route end users to a particular endpoint that you specify based on the end user’s geographic location.
Health Checks and Failover - Amazon Route 53 can monitor the health and performance of your application as well as your web servers and other resources.
... and many more advanced DNS features.
You don't have to host your website on AWS to be able to use Route53, it will happily work with services deployed across private datacentres.
Unless you're a Facebook or Google pricing should be an issue either, starting from $0.40 per million requests (see pricing details).
Hope that helps :)
answered 6 mins ago
MLu
4,79011633
Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
– zypA13510
2 mins ago
add a comment |
up vote
0
down vote
What you need is exactly what Amazon Route53 DNS service offers:
Latency based routing - Route end users to the AWS region that provides the lowest possible latency.
Geo DNS - Route end users to a particular endpoint that you specify based on the end user’s geographic location.
Health Checks and Failover - Amazon Route 53 can monitor the health and performance of your application as well as your web servers and other resources.
... and many more advanced DNS features.
You don't have to host your website on AWS to be able to use Route53, it will happily work with services deployed across private datacentres.
Unless you're a Facebook or Google pricing should be an issue either, starting from $0.40 per million requests (see pricing details).
Hope that helps :)
answered 6 mins ago
MLu
4,79011633
Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
– zypA13510
2 mins ago
add a comment |
up vote
0
down vote
up vote
0
down vote
What you need is exactly what Amazon Route53 DNS service offers:
Latency based routing - Route end users to the AWS region that provides the lowest possible latency.
Geo DNS - Route end users to a particular endpoint that you specify based on the end user’s geographic location.
Health Checks and Failover - Amazon Route 53 can monitor the health and performance of your application as well as your web servers and other resources.
... and many more advanced DNS features.
You don't have to host your website on AWS to be able to use Route53, it will happily work with services deployed across private datacentres.
Unless you're a Facebook or Google pricing should be an issue either, starting from $0.40 per million requests (see pricing details).
Hope that helps :)
answered 6 mins ago
MLu
4,79011633
What you need is exactly what Amazon Route53 DNS service offers:
Latency based routing - Route end users to the AWS region that provides the lowest possible latency.
Geo DNS - Route end users to a particular endpoint that you specify based on the end user’s geographic location.
Health Checks and Failover - Amazon Route 53 can monitor the health and performance of your application as well as your web servers and other resources.
... and many more advanced DNS features.
You don't have to host your website on AWS to be able to use Route53, it will happily work with services deployed across private datacentres.
Unless you're a Facebook or Google pricing should be an issue either, starting from $0.40 per million requests (see pricing details).
Hope that helps :)
answered 6 mins ago
MLu
4,79011633
answered 6 mins ago
MLu
4,79011633
answered 6 mins ago
MLu
4,79011633
answered 6 mins ago
MLu
4,79011633
4,79011633
Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
– zypA13510
2 mins ago
add a comment |
Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
– zypA13510
2 mins ago
Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
– zypA13510
2 mins ago
Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
– zypA13510
2 mins ago
add a comment |
yifan is a new contributor. Be nice, and check out our Code of Conduct.
yifan is a new contributor. Be nice, and check out our Code of Conduct.
yifan is a new contributor. Be nice, and check out our Code of Conduct.
yifan is a new contributor. Be nice, and check out our Code of Conduct.
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%2fserverfault.com%2fquestions%2f941506%2fcould-name-server-resolve-ip-address-dynamically-base-on-some-strategy%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
This sounds like a case for anycast.
– Ron Maupin
1 hour ago