Resolve AXFR host if DNS name is supplied #22
Merged
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.
Addresses #18
In our documentation we reference using a DNS name, which actually was not functional and wildly it never came up until recently. dnspython's
dns.query.xfr
anddns.query.tcp
expect an IP address to perform actions against otherwise it will error, it does not handle resolving it on it's own.This change adds a quick check to see if the host supplied by the user is an IPv4/IPv6 addresses or a DNS name, and if a DNS name is supplied it will resolve it to an IP to be passed off to
dns.query.xfr
anddns.query.tcp
Probably after #5 and this are merged will cut a new release