Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extra clarification #50831

Closed
gbaeke opened this issue Mar 24, 2020 — with docs.microsoft.com · 10 comments
Closed

Extra clarification #50831

gbaeke opened this issue Mar 24, 2020 — with docs.microsoft.com · 10 comments

Comments

Copy link

gbaeke commented Mar 24, 2020

Please clarify when the DHCP lease expires. If it is like virtual machines (>100 years), we can wait for a long time. Also clarify what "platform upgrade" means exactly.

Note there is a typo as well: upgarade instead of upgrade.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@Mike-Ubezzi-MSFT
Copy link
Contributor

@gbaeke Thank you for bringing this to our attention. I have corrected the spelling issue, and working to provide feedback with regard to DHCP leases. Platform upgrade could be better worded as it is vague to what exactly it refers.

@Mike-Ubezzi-MSFT
Copy link
Contributor

@srdan-bozovic-msft Is there additional clarification you can provide with regard to platform upgrade ? @stevestein for awareness.

Copy link

Is there a way to force the DHCP lease to renew? We implemented a CNAME for our Azure SQL MI and are getting "target principal name is incorrect". I'm hopeful the DHCP renew will get that working. Or perhaps not, there is a pretty big lack of information on setting up a custom DNS name for Azure SQL MI

@JustenCs
Copy link

I'd like to echo @ChrisMenegay's point above. How do we go about using our own DNS zones to reference SQL MI? I get the same 'error' If it were on prem, I'd add an SPN.
Thanks,
Charlie

@ChrisMenegay
Copy link

@JustenCs I ended up reaching out to Support. The DNS name must match the SQL MI. For example, if your DB is foo.mar1314234235.database.windows.net your local DNS MUST match the server name, so it could be: foo.contoso.com I did that and was able to connect, but I still have to "Trust Server Certificate" when connecting with AD accounts.

@JustenCs
Copy link

@ChrisMenegay thank you! Did you create an A record or CNAME?

@ChrisMenegay
Copy link

@JustenCs CNAME

@npigit
Copy link

npigit commented Apr 23, 2020

@Mike-Ubezzi-MSFT Have you received a feedback regarding the DHCP lease time? I would like to know how long it will to take effect when the custom DNS is configured after the azure SQL Managed Instance provisioning.

@Nash-Vegas
Copy link

Also need to know this information, thank you.

@srdan-bozovic-msft
Copy link
Member

updating dns servers on demand is now available and article is updated to reflect that
https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/synchronize-vnet-dns-servers-setting-on-virtual-cluster

as for the lease, it's indefinite but as we do updates monthly it would not take longer than month for the update

#please-close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants