App service tcp dns #127224
App service tcp dns #127224
Conversation
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull Request Overview
This PR documents a known limitation with App Service DNS resolution, specifically regarding the lack of fallback to TCP when a truncated UDP response is encountered. The changes add a new "Limitations" section to clearly describe this issue.
- Added a "Limitations" section detailing the lack of TCP fallback for DNS resolution.
- Provided an explanation of how using a non-EDNS-enabled DNS server might lead to failures.
Comments suppressed due to low confidence (1)
articles/app-service/overview-name-resolution.md:71
- [nitpick] Consider clarifying that this limitation may lead to intermittent DNS resolution failures and, if available, include a reference to Microsoft's support documentation as evidence to support this statement.
- App Service does not support falling back to DNS resolution over TCP when it encounters a truncated response over UDP. Configuring App Services to use a DNS server which does not implement EDNS to negotiate UDP responses larger than the standard 512 byte limit may result in DNS resolution failures.
|
@maciejporebski : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 4ad4010: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@madsd - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
We've encountered this limitation recently and I was not able to find this limitation documented anywhere. The limitation was confirmed by Microsoft Support. If this document is not the right place for this could you suggest a better home for documenting this limitation.