Dig can ask a specific DNS server by placing @server before the name. This is one of the fastest ways to compare what different resolvers see.

dig @1.1.1.1 example.com A
dig @8.8.8.8 example.com A
dig @9.9.9.9 example.com A

Why resolver comparison matters

DNS is cached. After a change, one resolver may still return the old value while another resolver already has the new one. Resolver comparison helps you decide whether the authoritative DNS is wrong or whether a cache simply has not expired.

Query the authoritative name server

When you know the authoritative name server, query it directly. That shows what the DNS provider is publishing before recursive cache gets involved.

dig example.com NS
dig @ns1.example-dns.net example.com A

Be careful with private resolvers

Corporate networks and VPNs sometimes use split-horizon DNS. They may return internal answers that public resolvers cannot see. If a result only appears on a private resolver, do not assume it is public DNS.