Keep useful evidence of a DNS incident

Capture enough context to reproduce a problem, rather than saving only an IP address.

Record the input and time

Write down the full name, query type and time zone. A report that only says “the website is down” cannot distinguish a wrong address, different caches or an HTTP failure. Keep the symptoms and the exact lookup scope together.

Preserve structure and readable text

The table supports quick inspection, JSON preserves fields, and CSV is useful for manual comparison. An export is a snapshot of one response and does not update after a provider changes its settings. Add the query time and environment to your notes.

Respect the limits of the evidence

Correct DNS does not rule out a TLS, application or firewall problem. This tool does not probe ports, test HTTP or run a global propagation check. Describe those investigations separately instead of inferring that they succeeded from a DNS answer.

This guide explains public DNS responses. Before changing production settings, check the documentation for your current domain and hosting providers.