Remove invalid IPv4 validation in DNS code #329 #330
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.
This is a fix for the issue with pool records that have a zero in one or more of their IP octets (e.g.
51.81.0.15
). #329The issue is that we are checking if one of the octets is a zero and if we get at least one we return without setting the DNS valid flag. If we don't get a zero we pass, but a zero in an IP octet is a perfectly valid value, so we should be passing as long as we aren't getting a null value.
Of course we could be more pedantic here as there are invalid values we could be looking for, but those are very unlikely to be received as valid DNS results, unless they are intentional (e.g. 127.0.0.1 or 0.0.0.0).
tl;dr this logic isn't really necessary and it should be enough to just remove it. Tested with a few pools and custom DNS records.