Why we need 168.63.129.16 IP address in custom DNS configured in Azure SQL Managed Instance and how it...
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 asked 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
add a comment |
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 asked 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
add a comment |
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 asked 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
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 asked 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
asked 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
asked 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
asked 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
asked 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
6,69222330
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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.
answered 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
add a comment |
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
});
}
});
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%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
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.
answered 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
add a comment |
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.
answered 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
add a comment |
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.
answered 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
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.
answered 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
edited 20 hours ago
answered 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
answered 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
answered 21 hours ago
Jovan MSFTJovan MSFT
6,69222330
6,69222330
add a comment |
add a comment |
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.
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%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
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
