-
Notifications
You must be signed in to change notification settings - Fork 129
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Follow CNAMES on all lookups by default (#397)
* CNAME following works for test lookups, integration tests failing tho * fixed return type so integration tests pass * add comments and clean up * add flag --follow-cnames * add DNAME integration test * add DNAME comments * add verbosity to test GH runner * remove verbosity flag for debugging * sigh...didn't add iterative flag to test * mistakenly misnamed the zdns exe in the test * add cname loop handling * lint * follow CNAMEs on external lookups too * fixed bugs * handle dnames, untested * fixed bugs with dname handling * PR comments * removed guard code that prevented following cnames with external lookups * return last good status when following CNAMEs, like dig * remove unneeded guard * return last good result/status if following cnames, fixes tests * return last good status if we hit error traversing cnames --------- Co-authored-by: Zakir Durumeric <zakird@gmail.com>
- Loading branch information
1 parent
c58d8ca
commit 22c38f1
Showing
7 changed files
with
263 additions
and
57 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.