1. 6

  2. 8

    The author doesn’t mention it but the @<domain> argument to dig specifies what dns server to query. This is useful for learning but also debugging DNS caching problems.

    For example, my Unifi router is bad at DNS. When I create a new subdomain my router will not resolve it until I restart its DNS resolver (dnsmasq). How did I figure this out? By doing dig mysubdomain.example.org @ and seeing the correct ANSWER ( is Cloudflare) and then doing dig mysubdomain.example.org @ and getting nothing (that private IP is my Unifi router/DNS server).