Manual review

Report a DNS problem.

Choose the closest category and send enough evidence to reproduce the problem. Reports do not automatically change filtering or access policy.

Report category

What went wrong?

Blocked domain

A legitimate domain appears filtered, rewritten or refused.

Resolver unavailable

DoH, DoT or ordinary approved DNS stopped resolving.

Certificate problem

A client reports an expired, mismatched or untrusted certificate.

Setup failure

The endpoint is correct but the device cannot connect after approval.

Access problem

An approved source address or ClientID is no longer accepted.

Security concern

Suspected compromise, abuse or disclosure requiring confidential handling.

Before reporting

Confirm the problem occurs while ScotNet DNS is enabled.
Record the approximate time and time zone.
Identify the transport: DoH, DoT, plain approved DNS or unknown.
For filtering issues, report the domain only—not passwords, tokens or sensitive full URLs.
Check service status for a known incident.

Report template

Copy this into the ScotNet contact route

Category: blocked domain / resolver unavailable / certificate / setup / access / security
Domain or endpoint affected:
Approximate date and time (include time zone):
Device / operating system / browser:
Transport: DoH / DoT / plain DNS / unknown
Source network changed recently? yes / no / unknown
Exact error or DNS response observed:
What troubleshooting has already been tried:
Why the domain appears legitimate (for filtering reports):
Can ScotNet contact you for more detail? yes / no

Do not include passwords, ClientIDs, authentication tokens, private full URLs or other sensitive information.

Open contact route Security contact

Review process

What happens next

1. Evidence check

The report is compared with active configuration, filter sources and relevant operational evidence.

2. Risk decision

ScotNet considers whether the issue is a false positive, access change, outage, compromise or client problem.

3. Proportionate action

A rule may be corrected, scoped, monitored or retained. Broad permanent exceptions are not the default.