Use Test-KTDNS v1.0.0 for Read-Only DNS Troubleshooting

Step 1

Download the versioned release files

Use either the complete ZIP or the direct script. Keep the checksum manifest and README with the script so the approved release can be verified and reviewed.

Supporting files: release README and SHA-256 manifest.

Step 2

Verify the script checksum before running it

From the release folder, use the manifest to compare the expected script checksum with the file you downloaded or extracted.

$expected = (Select-String -LiteralPath .\SHA256SUMS.txt -Pattern '  Test-KTDNS.ps1$').Line.Split()[0]
$actual = (Get-FileHash -LiteralPath .\Test-KTDNS.ps1 -Algorithm SHA256).Hash
$actual -eq $expected

The result must be True. The approved Test-KTDNS.ps1 SHA-256 is:

3BA1629A7A8DCF1EB82CE97114A9047529336667BCE1FB04F374F028E1340C1F

If the comparison is false, stop and obtain the release again from the KrippyTech Downloads page.

Step 3

Review the source and its boundaries

Read Test-KTDNS.ps1 before execution. Confirm that the parameters, supported types, DnsOnly setting, stable output object, and terminating-error behavior match the task you intend to perform.

The script performs DNS queries only. It does not use LLMNR or NetBIOS fallback, launch programs, or accept pipeline input.

Step 4

Use targeted Unblock-File only when appropriate

Windows may mark a browser-downloaded script as originating from the Internet. After the checksum is verified and the source is reviewed, RemoteSigned may permit the script after removing that mark from this file only.

Unblock-File -LiteralPath .\Test-KTDNS.ps1

This step is not a substitute for checksum verification or source review. Do not apply a broad unblock operation and do not bypass or globally change execution policy.

Step 5

Run a basic DNS query

The default record type is A. These documentation-safe examples come from the script's approved help.

.\Test-KTDNS.ps1 -Name example.com

.\Test-KTDNS.ps1 -Name example.com -Type MX

.\Test-KTDNS.ps1 -Name localhost -Type A

Supported record types are A, AAAA, CNAME, MX, NS, PTR, SRV, and TXT.

Step 6

Query a specifically approved DNS resolver

When -Server is omitted, Windows uses DNS servers configured on the active network interface. Use the optional parameter only for an approved resolver.

.\Test-KTDNS.ps1 -Name example.com -Type TXT -Server '<dns-server-ip>'

Replace the placeholder with the authorized DNS server IP address or host name. Do not send internal names to an untrusted resolver.

Step 7

Read the normalized output

Every returned record uses the same property set. Fields that do not apply to the record type are $null.

.\Test-KTDNS.ps1 -Name example.com -Type A |
    Format-Table RecordName, RecordType, TTL, Value

Step 8

Treat expected failures as evidence

Invalid names, resolvers, or unsupported record types fail during parameter binding. DNS failures are terminating errors because the approved script calls Resolve-DnsName with -ErrorAction Stop.

try {
    $result = .\Test-KTDNS.ps1 -Name example.com -Type A
}
catch {
    Write-Error "DNS query failed: $($_.Exception.Message)"
}

A failure may indicate that the name or requested type has no answer, the resolver cannot be reached, the request was refused, or another DNS or connectivity condition interrupted the query. Read the error in the context of the exact name, record type, resolver, and time tested.