-
Notifications
You must be signed in to change notification settings - Fork 1
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
resolve-dns throw a powershell error with non existent domain #3
Comments
Hey @wyldspyder, thanks for reaching out. I can't seem to reproduce this on my machine. I get a normal NXDOMAIN response when looking up that record, not an exception even if I query the same
I get essentially the same result from dig.
|
Hi @rmbolger ! thanks for the fast answer !! I think I might have an idea but i'm not an expert ont this. As your test, i've tested it on my personal computer and work exactly the same as you. The problem arose when I use it with my work computer, and I know that we can only issue DNS request to specific server only, as any DNS request will be blocked by the firewall, can it be ?? |
That could definitely be it. The error message you got was specifically a "connection timed out" error which means either your machine was being blocked from reaching the designated nameserver or the nameserver itself was offline or not responding. |
As the tile said, the module throw a powershell error and not a "inexistent domain" with an inexistent domain.
Ex:
The text was updated successfully, but these errors were encountered: