Why we need 168.63.129.16 IP address in custom DNS configured in Azure SQL Managed Instance and how it...












-1















I want to setup custom DNS for Azure SQL Managed Instance and according to the documentation I need to put Azure Recursive Resolver DNS IP address 168.63.129.16 at the end of the virtual network DNS list.



Would adding 168.63.129.16 to DNS list affect name resolution in the virtual network?






azure dns azure-sql-managed-instance







share|improve this question



























    -1















    I want to setup custom DNS for Azure SQL Managed Instance and according to the documentation I need to put Azure Recursive Resolver DNS IP address 168.63.129.16 at the end of the virtual network DNS list.



    Would adding 168.63.129.16 to DNS list affect name resolution in the virtual network?






    azure dns azure-sql-managed-instance







    share|improve this question

























      -1












      -1








      -1








      I want to setup custom DNS for Azure SQL Managed Instance and according to the documentation I need to put Azure Recursive Resolver DNS IP address 168.63.129.16 at the end of the virtual network DNS list.



      Would adding 168.63.129.16 to DNS list affect name resolution in the virtual network?






      azure dns azure-sql-managed-instance







      share|improve this question














      I want to setup custom DNS for Azure SQL Managed Instance and according to the documentation I need to put Azure Recursive Resolver DNS IP address 168.63.129.16 at the end of the virtual network DNS list.



      Would adding 168.63.129.16 to DNS list affect name resolution in the virtual network?






      azure dns azure-sql-managed-instance




      azure dns azure-sql-managed-instance






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 21 hours ago









      Jovan MSFTJovan MSFT

      6,69222330




      6,69222330
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Azure SQL Managed Instance uses DNS to resolve the IP of the Azure management service that controls the instance and where the health information are sent. If you want to put your own custom DNS, Managed Instance requires this rule as a fallback option in the case that custom DNS servers are not responding and there is a risk that the Managed Instance cannot access Azure managements services in order to keep running properly.




          Note - this is just one way of achieving our requirement that custom
          DNS server has to provide public DNS name resolution. In case of
          having custom DNS server on-premises this is even not possible.




          Adding 168.63.129.16 to DNS list will affect name resolution in your VNet only if all of your DNS servers are down. DNS resolution falls back down the list only if DNS server upper in the list is not responding. If the response is that the name could not be resolved that answer is simply accepted without propagating request further.






          share|improve this answer

























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

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


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54250605%2fwhy-we-need-168-63-129-16-ip-address-in-custom-dns-configured-in-azure-sql-manag%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









            0














            Azure SQL Managed Instance uses DNS to resolve the IP of the Azure management service that controls the instance and where the health information are sent. If you want to put your own custom DNS, Managed Instance requires this rule as a fallback option in the case that custom DNS servers are not responding and there is a risk that the Managed Instance cannot access Azure managements services in order to keep running properly.




            Note - this is just one way of achieving our requirement that custom
            DNS server has to provide public DNS name resolution. In case of
            having custom DNS server on-premises this is even not possible.




            Adding 168.63.129.16 to DNS list will affect name resolution in your VNet only if all of your DNS servers are down. DNS resolution falls back down the list only if DNS server upper in the list is not responding. If the response is that the name could not be resolved that answer is simply accepted without propagating request further.






            share|improve this answer






























              0














              Azure SQL Managed Instance uses DNS to resolve the IP of the Azure management service that controls the instance and where the health information are sent. If you want to put your own custom DNS, Managed Instance requires this rule as a fallback option in the case that custom DNS servers are not responding and there is a risk that the Managed Instance cannot access Azure managements services in order to keep running properly.




              Note - this is just one way of achieving our requirement that custom
              DNS server has to provide public DNS name resolution. In case of
              having custom DNS server on-premises this is even not possible.




              Adding 168.63.129.16 to DNS list will affect name resolution in your VNet only if all of your DNS servers are down. DNS resolution falls back down the list only if DNS server upper in the list is not responding. If the response is that the name could not be resolved that answer is simply accepted without propagating request further.






              share|improve this answer




























                0












                0








                0







                Azure SQL Managed Instance uses DNS to resolve the IP of the Azure management service that controls the instance and where the health information are sent. If you want to put your own custom DNS, Managed Instance requires this rule as a fallback option in the case that custom DNS servers are not responding and there is a risk that the Managed Instance cannot access Azure managements services in order to keep running properly.




                Note - this is just one way of achieving our requirement that custom
                DNS server has to provide public DNS name resolution. In case of
                having custom DNS server on-premises this is even not possible.




                Adding 168.63.129.16 to DNS list will affect name resolution in your VNet only if all of your DNS servers are down. DNS resolution falls back down the list only if DNS server upper in the list is not responding. If the response is that the name could not be resolved that answer is simply accepted without propagating request further.






                share|improve this answer















                Azure SQL Managed Instance uses DNS to resolve the IP of the Azure management service that controls the instance and where the health information are sent. If you want to put your own custom DNS, Managed Instance requires this rule as a fallback option in the case that custom DNS servers are not responding and there is a risk that the Managed Instance cannot access Azure managements services in order to keep running properly.




                Note - this is just one way of achieving our requirement that custom
                DNS server has to provide public DNS name resolution. In case of
                having custom DNS server on-premises this is even not possible.




                Adding 168.63.129.16 to DNS list will affect name resolution in your VNet only if all of your DNS servers are down. DNS resolution falls back down the list only if DNS server upper in the list is not responding. If the response is that the name could not be resolved that answer is simply accepted without propagating request further.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 20 hours ago

























                answered 21 hours ago









                Jovan MSFTJovan MSFT

                6,69222330




                6,69222330






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • 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%2fstackoverflow.com%2fquestions%2f54250605%2fwhy-we-need-168-63-129-16-ip-address-in-custom-dns-configured-in-azure-sql-manag%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

                    Homophylophilia

                    Image
                    Haec pagina ad tempus protecta est ob maleficia perpetua. Quaesemus, emendationes suggere in pagina disputationis vel magistratum ad hanc deprotegendam pete. Homophylophilia Hyacinthus complexus ab amante suo Apolline, in pictura Mors Hyacinthi quam Jean Broc pinxit. Homophylophilia est sui sexus vel generis amor vel mores romantici vel sexuales, res venerea masculina in masculos, aut mulier in mulieres appetentes. Hoc ingenium sexuale est "exemplar permanens vel inclinatio ad experiendam sexualem, adfectionalem, vel romanticam vim attrahendi," praecipue vel solum ex hominibus eiusdem sexús; notio "etiam ad hominis iudicium identitatis privatae socialisque in illis attractionibus conditum refert, in moribus quoque qui illos exprimant, et in societate communitatis aliorum qui illos communicent." [1] [2] Per aevos alii aliter rem definiverunt, sed Occidentali nostrae aetatis cultu civili non tantum ad ipsa acta erotica spectat, sed etiam igitur
                    Read more

                    Updating UILabel text programmatically using a function

                    Image
                    0 so I am trying to update the UIlabel text using a func. I have seen few other questions like mine and I tried their method but it doesn't work. fun returns no value when used in the UIlabel. I have shown my code below.It has to be noted that when I use the function in viewdidload I can retrieve the data. lazy var name: UILabel = { let lb = UILabel() lb.text? = getthename() lb.lineBreakMode = NSLineBreakMode.byWordWrapping lb.textColor = .mainGreen lb.textAlignment = .left lb.font = UIFont.boldSystemFont(ofSize:12.0) return lb }() func getthename() -> String { var wins : String = "" let ud = (Auth.auth().currentUser?.uid) self.ref = Database.database().reference() self.ref.child("Users").child(ud!).observeSingleEvent(of: .value, with: {(snapshot) in
                    Read more

                    Cloud Functions - OpenCV Videocapture Read method fails for larger files from cloud storage

                    Image
                    0 I created a cloud function to read a video file from cloud storage and read frames and create an image for each frame. This function works for small files which is 1-2 MB, However, this method fails while reading larger file 130 MB. import cv2 from google.cloud import storage vidcap = cv2.VideoCapture("https://storage.googleapis.com/[bucker_name]/[filename.mp4]") if vidcap.isOpened(): vidcap.open("https://storage.googleapis.com/[bucker_name]/[filename.mp4]") success,image = vidcap.read() print(success) Expected the print will return true and an image will hold an image of a first frame. python-3.x function opencv cloud share | improve this question
                    Read more