-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
throw preventing all Accepted Domains DNS records from being evaluated #1477
Comments
Hi, thanks for reporting this. I agree, an exception thrown while resolving one domain shouldn't stop the other domains from being tested. I will open an issue to revisit that behavior. That said, would you mind sharing what specific exception is causing "Failed to resolve..." to throw? A simple NXDOMAIN, empty answer section, or even a one-time network failure wouldn't be enough to trigger it. Both the traditional DNS query and the DoH fallback would have to repeatedly fail to reach that point. The specific exception should be printed as part of the message, "Query resulted in exception, ..." See #1479. |
I wasn't seeing a throw in the console output, so it was making it difficult to find. (I anonymized the domains returned.)
I imported the ExportEXOProvider.psm1 as a module, and ran the following:
That is where I saw the throw.
After I Its unclear to me why I'm not seeing the throw in the console when running |
When running exo report, I'm seeing
Failed to resolve ...
but for only one domain per record type. At first I thought that was great as there is little to review. Once I realized if one of these domains appeared, so should others due to our split DNS architecture, I know there was a bug.ScubaGear/PowerShell/ScubaGear/Modules/Providers/ExportEXOProvider.psm1
Line 353 in c580eb1
When
throw
is called, the routine is escaped and no additional Accepted Domains are processed for that record type. When I replacedthrow
withWrite-Warning
, all the Accepted Domains were evaluated and showed on-screen.The text was updated successfully, but these errors were encountered: