Could name server resolve IP address dynamically base on some strategy?











up vote
4
down vote

favorite
1












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?










share|improve this question









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
    2 hours ago















up vote
4
down vote

favorite
1












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?










share|improve this question









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
    2 hours ago













up vote
4
down vote

favorite
1









up vote
4
down vote

favorite
1






1





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?










share|improve this question









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






share|improve this question









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.











share|improve this question









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.









share|improve this question




share|improve this question








edited 51 mins ago









Ron Maupin

2,0101512




2,0101512






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 2 hours 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
    2 hours ago


















  • This sounds like a case for anycast.
    – Ron Maupin
    2 hours ago
















This sounds like a case for anycast.
– Ron Maupin
2 hours ago




This sounds like a case for anycast.
– Ron Maupin
2 hours ago










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.






share|improve this answer




























    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 shouldn't be an issue either, starting from $0.40 per million requests (see pricing details).



    Hope that helps :)






    share|improve this answer























    • Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
      – zypA13510
      50 mins ago










    • @zypA13510 indeed, fixed. Thanks :)
      – MLu
      44 mins ago











    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "2"
    };
    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',
    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
    });


    }
    });






    yifan is a new contributor. Be nice, and check out our Code of Conduct.










     

    draft saved


    draft discarded


















    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

























    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.






    share|improve this answer

























      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.






      share|improve this answer























        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.






        share|improve this answer












        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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 1 hour ago









        Ron Maupin

        2,0101512




        2,0101512
























            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 shouldn't be an issue either, starting from $0.40 per million requests (see pricing details).



            Hope that helps :)






            share|improve this answer























            • Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
              – zypA13510
              50 mins ago










            • @zypA13510 indeed, fixed. Thanks :)
              – MLu
              44 mins ago















            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 shouldn't be an issue either, starting from $0.40 per million requests (see pricing details).



            Hope that helps :)






            share|improve this answer























            • Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
              – zypA13510
              50 mins ago










            • @zypA13510 indeed, fixed. Thanks :)
              – MLu
              44 mins ago













            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 shouldn't be an issue either, starting from $0.40 per million requests (see pricing details).



            Hope that helps :)






            share|improve this answer














            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 shouldn't be an issue either, starting from $0.40 per million requests (see pricing details).



            Hope that helps :)







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 44 mins ago

























            answered 54 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
              50 mins ago










            • @zypA13510 indeed, fixed. Thanks :)
              – MLu
              44 mins ago


















            • Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
              – zypA13510
              50 mins ago










            • @zypA13510 indeed, fixed. Thanks :)
              – MLu
              44 mins ago
















            Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
            – zypA13510
            50 mins ago




            Unless you're a Facebook or Google pricing should be an issue either I believe you meant shouldn't?
            – zypA13510
            50 mins ago












            @zypA13510 indeed, fixed. Thanks :)
            – MLu
            44 mins ago




            @zypA13510 indeed, fixed. Thanks :)
            – MLu
            44 mins ago










            yifan is a new contributor. Be nice, and check out our Code of Conduct.










             

            draft saved


            draft discarded


















            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.















             


            draft saved


            draft discarded














            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





















































            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

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

            Calculate evaluation metrics using cross_val_predict sklearn

            Insert data from modal to MySQL (multiple modal on website)