Azure-docs: Is there anything special about the DNS name "privatelink.postgres.database.azure.com"

[atrauzzi]

...or can we choose anything we want, so long as we point to the right IP address?

---

Document Details

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

• ID: 78271f92-2709-dcaa-4771-29564329da05
• Version Independent ID: 5b34e1bb-898e-4360-1c1b-8c577c619021
• Content: Private Link - Azure portal - Azure Database for PostgreSQL - Single server
• Content Source: articles/postgresql/howto-configure-privatelink-portal.md
• Service: postgresql
• GitHub Login: @kummanish
• Microsoft Alias: manishku

[KalyanChanumolu-MSFT]

@atrauzzi Thank you for reaching out.

@kummanish Could you please help here?

[kummanish]

@atrauzzi this is the default DNS name that is tightly integrated with the Private link created for your PostgreSQL server. https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-dns

YOu can have your custom DNS server as long as you have the FQDN to IP (A Record) in that.

[atrauzzi]

Sorry, @kummanish , your response is a little confusing. Saying _"tightly integrated"_ and then saying it can be custom means it isn't _"tightly integrated"_.

Is it not possible to just put some notes in the document mentioning that the DNS showed is mostly as an example?

[kummanish]

I have added link to the DNS zone configuration. https://docs.microsoft.com/en-us/azure/postgresql/howto-configure-privatelink-portal

[atrauzzi]

Did that in any way directly answer my question?

How is this helpful?

[kummanish]

I have updated the doc with the changes mentioned. The link is still there since it is important for people who want to read more about it.

[kummanish]

please-close

[atrauzzi]

I don't see any changes associated with this ticket... How exactly have you clearly answered my question?

[kummanish]

please-close

[kummanish]

Its already published here : https://docs.microsoft.com/en-us/azure/postgresql/howto-configure-privatelink-portal#create-a-private-endpoint

Let me know if you cannot see it.

[atrauzzi]

What did you change?

[kummanish]

I have added this note:
Use the predefined private DNS zone for your service or create a new one. Refer to the Azure services DNS zone configuration for details.

The content of the DNS zone cannot be replicated in multiple docs. So having the link to read more is the preferred way. Let me know if this clarifies your question. thanks.

[atrauzzi]

No it didn't at all. You aren't speaking directly with the phrase "or create a new one". It's just vague English and doesn't offer a well anchored understanding of the degree of flexibility.

It would be better to say something to the effect of "...you are free to provide a DNS zone with a name other than the default or any examples found here..."

Phrasing it that way makes it clear what you're talking about, acknowledges the tutorial context as being only a sample and reduces it from being too vague in the middle of so much other information.

[kummanish]

The idea is for making it easy to use for customer. So the preferred way is through predefined DNS zone name. Therefore I can rewrite this as below. This does make it clear that it is just an option for customers to try.

"Use the predefined private DNS zone for your service or provide your preferred DNS zone name. Refer to the Azure services DNS zone configuration for details."