Skip to content

Clarify internal IP handling in Private DNS service - #2052

Open
Christopher Brumm (crmhh) wants to merge 1 commit into
MicrosoftDocs:mainfrom
crmhh:patch-1
Open

Clarify internal IP handling in Private DNS service#2052
Christopher Brumm (crmhh) wants to merge 1 commit into
MicrosoftDocs:mainfrom
crmhh:patch-1

Conversation

@crmhh

Copy link
Copy Markdown

Updated the explanation of the Private DNS service to clarify the handling of internal IP addresses.

Synthetic IPs are only used if FQDNs are configured as App Segments. The Private DNS feature (using NRPT) returns internal/orginal IPs.

I've corrected the texts but in the picture is also a wrong reference to a syntetic IP -> https://learn.microsoft.com/en-us/entra/global-secure-access/media/concept-private-name-resolution/queries.png

Updated the explanation of the Private DNS service to clarify the handling of internal IP addresses.

Synthetic IPs are only used if FQDNs are configured as App Segments. The Private DNS feature (using NRPT) returns internal/orginal IPs.

I've corrected the texts but in the picture is also a wrong reference to a syntetic IP -> https://learn.microsoft.com/en-us/entra/global-secure-access/media/concept-private-name-resolution/queries.png
@prmerger-automator

Copy link
Copy Markdown
Contributor

Christopher Brumm (@crmhh) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Jay (@HULKsmashGithub)

1 similar comment
@prmerger-automator

Copy link
Copy Markdown
Contributor

Christopher Brumm (@crmhh) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Jay (@HULKsmashGithub)

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 8c7993c:

✅ Validation status: passed

File Status Preview URL Details
docs/global-secure-access/concept-private-name-resolution.md ✅Succeeded

For more details, please refer to the build report.

@v-regandowner

Copy link
Copy Markdown
Contributor

Celeste de Guzman (@CelesteDG)

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants