d-Updated Azure plugin NS record#4383
Merged
yongtang merged 1 commit intocoredns:masterfrom Jan 11, 2021
Merged
Conversation
Signed-off-by: gunadhya <6939749+gunadhya@users.noreply.github.com>
Codecov Report
@@ Coverage Diff @@
## master #4383 +/- ##
=======================================
Coverage 55.46% 55.46%
=======================================
Files 223 223
Lines 9924 9924
=======================================
Hits 5504 5504
Misses 3963 3963
Partials 457 457 Continue to review full report at Codecov.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Signed-off-by: gunadhya 6939749+gunadhya@users.noreply.github.com
1. Why is this pull request needed and what does it do?
Updates the doc for azure plugin to clarify support for NS record.
2. Which issues (if any) are related?
Fixes #4332
3. Which documentation changes (if any) need to be made?
No
4. Does this introduce a backward incompatible change or deprecation?
No