Skip to content

Adds not regarding "DNS name does not exist" error. #6

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

johnnymatthews
Copy link

I encountered this error when attempting to run the Resolve-DnsName -Type txt proto.on.quad9.net. command:

Resolve-DnsName : proto.on.quad9.net. : DNS name does not exist
At line:1 char:1
+ Resolve-DnsName -Type txt proto.on.quad9.net.
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (proto.on.quad9.net.:String) [Resolve-DnsName], Win32Exception
    + FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

I was being a bit of an idiot and completely forgot to disable my VPN client first. Once I did that, the error went away and I was able to continue using this FAQ guide.

Repo owners: feel free to edit or delete this PR if it doesn't fit.

I encountered this error when attempting to run the `Resolve-DnsName -Type txt proto.on.quad9.net.` command:

```
Resolve-DnsName : proto.on.quad9.net. : DNS name does not exist
At line:1 char:1
+ Resolve-DnsName -Type txt proto.on.quad9.net.
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (proto.on.quad9.net.:String) [Resolve-DnsName], Win32Exception
    + FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName
```

I was being a bit of an idiot and completely forgot to disable my VPN client first. Once I did that, the error went away and I was able to continue using this FAQ guide.
@johnnymatthews
Copy link
Author

Just seen this in the repo's README:

Pull requests are allowed for typos and minor corrections only. New articles will likely not be merged, since they will need to be translated.

Not sure if this counts as a new article, but no worries if this doesn't get merged. It's in this repo's history now, so at least this problem is searchable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant