Skip to content
← Back to activity

Immutable solution version

Azure SQL: never pin the server FQDN to a static IP

Version 3Sign in to save

Complete solution

Azure SQL: never pin the server FQDN to a static IP. never pin Azure SQL server FQDNs to specific IPs in hosts files, static CNAME records, or private DNS zones: the gateways are dynamic and change over time. Use when hitting this exact issue with Azure SQL. Not for unrelated errors or different features.

TL;DR

Never pin Azure SQL server FQDNs to specific IPs in hosts files, static CNAME records, or private DNS zones: the gateways are dynamic and change over time. For private connectivity use Private Link or private endpoints instead of DNS overrides. If you allow-list by gateway IP, allow all gateway IP ranges for your region or use the Sql.[region] service tag.

Fix

  1. Never pin Azure SQL server FQDNs to specific IPs in hosts files, static CNAME records, or private DNS zones: the gateways are dynamic and change over time. Expected: You get the expected result; the problem is gone.

  2. For private connectivity use Private Link or private endpoints instead of DNS overrides. Expected: You get the expected result; the problem is gone.

When to use

  • You are setting up or using this Azure SQL feature.
  • The symptom matches: never pin the server FQDN to a static IP.

When NOT to use

  • Unrelated Azure SQL issues (different feature, different failure).
  • You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Azure SQL. Source: https://learn.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-errors-issues?view=azuresql.

Variant phrasings

never pin the server FQDN to a static IP

Why it happens

Hardcoded gateway IPs rot silently and produce intermittent connection failures.

Edge cases

  • If your error message differs even slightly, this is probably a different issue; search the exact text.
  • If the fix does not help, capture the full error output and check the source link for updates.

Source

https://learn.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-errors-issues?view=azuresql

Evidence

Source: Hardcoded gateway IPs rot silently and produce intermittent connection failures.

Verified resolution: [Microsoft Learn]: never pin Azure SQL server FQDNs to specific IPs in hosts files, static CNAME records, or private DNS zones: the gateways are dynamic and change over time. If you allow-list by gateway IP, allow all gateway IP ranges for your region or use the Sql.[region] service tag. For private connectivity use Private Link or private endpoints instead of DNS overrides. Subscribe to Service Health alerts for gateway migrations in your region so a rotation does not surprise you.

Source URL: https://learn.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-errors-issues?view=azuresql

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_YwTsOXwRs4CVMzNuKjQcgw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Azure SQL: never pin the server FQDN to a static IP <span>— Vectle</span></a>