To check a DNS TXT record on Windows, run nslookup -type=TXT followed by the exact DNS name the service asked you to publish. Querying the main domain is not a substitute for querying a named label beneath it. A successful answer shows what the selected DNS resolver returned; it does not prove that an external service has accepted your verification.
This workflow is for collecting read-only evidence before editing DNS again or repeatedly pressing a verification button. Use domains you administer and approved resolvers. Do not send private internal names to an external DNS service, and do not publish verification values in public support discussions unnecessarily.
Separate the record name from its value
Read the service’s instructions and identify three distinct details: the record type, the complete owner name, and the expected text value. A DNS provider may label the owner-name field Host or Name. Do not paste the verification value into that field merely because both are text.
For a hypothetical setup, imagine a service asks for a TXT record at _service-check.example.com. Querying example.com asks about a different DNS owner name. Likewise, a record at another subdomain does not establish that the requested owner name exists.
The example label here is invented for explanation; it is not a universal service requirement. Use the name supplied by your actual provider. Check whether your DNS editor automatically appends the zone name before changing anything: the goal is the intended complete name, not a duplicated domain suffix.
Query TXT explicitly from Command Prompt
Open Command Prompt and run this documentation-domain example:
nslookup -type=TXT example.com.The -type=TXT option asks for text records rather than relying on the default address-record query. The trailing period makes the domain name absolute. Microsoft documents command-line options and explains that, without a second server argument, nslookup uses its default DNS server.
For the hypothetical labelled record, the corresponding query is:
nslookup -type=TXT _service-check.example.com.Replace that entire example name with the exact owner name from your instructions before using it for a real investigation. These examples do not promise that either documentation name currently has a TXT answer. Record the complete command, observation time, resolver address, and returned message. Do not omit the label when copying the evidence into a private support ticket.
Read the response before deciding to edit DNS
- TXT text appears: compare the returned text with the value the service supplied. Unrelated TXT records at the same name do not establish that your required value is present.
- No records: Microsoft distinguishes a valid name without records of the requested type from a nonexistent name. Keep the record type in your evidence.
- Nonexistent domain: recheck the complete owner name and spelling. This response is not the same as a TXT value mismatch.
- Timed out: the request did not receive a response within the applicable attempts and timeout. Do not report this as proof that the TXT record is absent.
- Server failure or refused: preserve the exact error. A resolver problem or refusal calls for different follow-up from correcting the record value.
The output also identifies the DNS server involved in the lookup. That server address is not your verification token. Avoid extracting whichever number or string appears first and calling it the answer.
Keep resolver evidence separate from verification acceptance
If the expected value is returned but verification still fails, stop cycling through speculative edits. Save the provider’s requested owner name and value, your lookup result, and the service’s precise error. Ask the service which name it checks and whether any additional account-side action is required.
A single resolver answer is not proof that every resolver has the same cached information. Nor does it prove domain ownership has been accepted, an email-authentication policy is correct, or mail will be delivered. Those conclusions require their own service-specific checks.
When a resolver comparison is actually warranted, follow the separate guide to comparing two approved DNS servers without changing Windows settings. Keep the same full owner name and TXT query type in both requests. Do not switch the computer’s network configuration just to repeat a read-only lookup.
Final checklist and common questions
- Did you use the exact owner name rather than only the main domain?
- Did you request TXT and distinguish returned text from an error?
- Did you compare the expected value privately and preserve the original instructions?
- Did the external service actually confirm verification, rather than merely accepting a button click?
Does this command change my records? No. It queries DNS; it does not edit the zone, so there is no DNS change from these commands to roll back. Should I remove other TXT records? Not as a troubleshooting shortcut. They may belong to unrelated services; establish ownership and dependencies before proposing an authorised change.
Sources: Microsoft’s nslookup reference supports command framing and error distinctions; the set type reference identifies TXT as text information.
Safety: This tutorial is for educational purposes. Test carefully before using steps in production. The site owner is not responsible for misuse, damage, data loss or production issues.
