July 17, 2022 dig +trace follows the whole chain from the beginning - it queries root servers, then .info servers then your namservers. Thus it avoids any caching resolvers, and also avoids propagation issues. dig +notrace (the default) queries your default DNS resolver (on Linux, whatever specified in /etc/resolv.conf). Trace Queries linkNS Record linkNo NS returned during normal (+notrace) query. It does return during a +trace query to Google DNS. dig adoptiontrafficking.org @8.8.8.8 ns ;; QUESTION SECTION: ;adoptiontrafficking.org. IN NS dig adoptiontrafficking.org @8.8.8.8 ns +trace adoptiontrafficking.org. 3600 IN NS na1.ns.ramnode.com. adoptiontrafficking.org. 3600 IN NS na2.ns.ramnode.com. adoptiontrafficking.org. 3600 IN DS 6526 8 2 1B9ACA8A9DA2BB3F90C81715C2B781443E773DC77F045BB9D9304CE1 74086687 adoptiontrafficking.org. 3600 IN RRSIG DS 8 2 3600 20220730152415 20220709142415 52626 org. WHDbI/sImiZOrATJrjIkZx8HXc+FIGlz4nk9Y5JP7dJoVXGq3yfH8cPQ VcwTVAuySC/g7vorV+uSdj3kAWSAnBfTTgRZhI3V13HpazIX+K4s1UxO Po3gjS7AFkXWbzHnW4IF1TzXnC5Eyc/IGzP/qlNcnXbgN1QOGDhg+18W qfE= ;; Received 313 bytes from 199.19.56.1#53(a0.org.afilias-nst.info) in 99 ms adoptiontrafficking.org. 14400 IN A 107.161.23.47 adoptiontrafficking.org. 86400 IN NS na2.ns.ramnode.com. adoptiontrafficking.org. 86400 IN NS na1.ns.ramnode.com. ;; Received 162 bytes from 192.184.93.132#53(na2.ns.ramnode.com) in 26 ms Why doesn’t it show in the normal query? A Record link dig @8.8.8.8 -t a adoptiontrafficking.org +trace ; <<>> DiG 9.11.5-P4-5.1+deb10u7-Debian <<>> @8.8.8.8 -t a adoptiontrafficking.org +trace ; (1 server found) ;; global options: +cmd . 15561 IN NS a.root-servers.net. . 15561 IN NS b.root-servers.net. . 15561 IN NS c.root-servers.net. . 15561 IN NS d.root-servers.net. . 15561 IN NS e.root-servers.net. . 15561 IN NS f.root-servers.net. . 15561 IN NS g.root-servers.net. . 15561 IN NS h.root-servers.net. . 15561 IN NS i.root-servers.net. . 15561 IN NS j.root-servers.net. . 15561 IN NS k.root-servers.net. . 15561 IN NS l.root-servers.net. . 15561 IN NS m.root-servers.net. . 15561 IN RRSIG NS 8 0 518400 20220729170000 20220716160000 20826 . CY4xTG39Z+1q5Zsx3rPFGYdnfv82kkCe1AqsK6BRH9y6OIXk+Vw8DBC1 QDRjaq72hLCs1bCdg/bAQB3BDjV32vBPMmzoyBuJCuHzkaG02r1rngsJ SytarCE/vyr3HBNxwqXazwYEGoLhKI+QBlwpGJBW7FEwdTEVqb2/LWcP fa3qiQHXY47pNg1OkAuxaJOlsU8yImIUSvD4hkLfek311n2mprjzBM48 kABgdH9oDOdvGJmFfsQTpfq64wMENSmTVmBBdEdMNoFC0IFpbOwsd3aF 4e0holTFc/b8fjn944UM7Q11TyZKP6KlWLP+CbB3UDxF/HiQHHlVuASj zqSh+A== ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms org. 172800 IN NS d0.org.afilias-nst.org. org. 172800 IN NS a0.org.afilias-nst.info. org. 172800 IN NS b2.org.afilias-nst.org. org. 172800 IN NS a2.org.afilias-nst.info. org. 172800 IN NS b0.org.afilias-nst.org. org. 172800 IN NS c0.org.afilias-nst.info. org. 86400 IN DS 26974 8 2 4FEDE294C53F438A158C41D39489CD78A86BEB0D8A0AEAFF14745C0D 16E1DE32 org. 86400 IN RRSIG DS 8 1 86400 20220730170000 20220717160000 20826 . lNpBs3hrPaWUsifbDeZULlXr6roQr+ZGbjLE7uL23B8XM6syXyPmR7Oq Exje/9u8+VVApz3tg/wcFSpCCf6fuWSxKP2de4aznaf0tGW2uKExbwhb EQOp6prgt2gDFFLwrbCxA2WxTsjP2CDXAgnzh01zGrD0dvD+9JmneEgZ 5MXrqUzjV1ou+Crcm25ys4QpoK3PI7SX17uQ4IleO/Gx6cLfk8wDN03M cLOTMPxzTOzQz364erDswQdcj6AB59xm/NRBblds2dfAnAJJkoQdUpO1 gc0hsW9xGSGaZpnpMOF2lwvhh/sYYvLmT5H1LeBSNgUWMoggs6r8oowP GW4DcQ== ;; Received 792 bytes from 202.12.27.33#53(m.root-servers.net) in 11 ms adoptiontrafficking.org. 3600 IN NS na1.ns.ramnode.com. adoptiontrafficking.org. 3600 IN NS na2.ns.ramnode.com. adoptiontrafficking.org. 3600 IN DS 6526 8 2 1B9ACA8A9DA2BB3F90C81715C2B781443E773DC77F045BB9D9304CE1 74086687 adoptiontrafficking.org. 3600 IN RRSIG DS 8 2 3600 20220807152417 20220717142417 52626 org. nDwroxQ6ysHlT8equlbxGRNpSs5UIwWdkQPJlobdZsOgjHmpLEjSJYGA CHHbvnIoAZmB+laBH05jNXgJvjuL5InpK8RkOXSbeOqwoAnEtLtdBOWE +8ktSt0/3QCrYRwTq8k8y1qvj2Am+3lS6aUpyNc5afNjieXk3bp5lEMQ Q0Y= ;; Received 313 bytes from 199.249.112.1#53(a2.org.afilias-nst.info) in 0 ms adoptiontrafficking.org. 14400 IN A 107.161.23.47 adoptiontrafficking.org. 86400 IN NS na2.ns.ramnode.com. adoptiontrafficking.org. 86400 IN NS na1.ns.ramnode.com. ;; Received 162 bytes from 192.184.93.132#53(na2.ns.ramnode.com) in 26 ms dig @8.8.8.8 -t a adoptiontrafficking.org ; <<>> DiG 9.11.5-P4-5.1+deb10u7-Debian <<>> @8.8.8.8 -t a adoptiontrafficking.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 444 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;adoptiontrafficking.org. IN A ;; Query time: 42 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sun Jul 17 13:53:46 PDT 2022 ;; MSG SIZE rcvd: 52 Workaround linkRouted my traffic behind a VPN. Not sure why I can’t resolve the servers, but using the VPN resolved the problem for now. Resources link Stack overflow - No good Not returning NameServer (Stack overflow) MX Records only show up in +trace SERVFAIL but works on +trace DNS fails +trace disagrees

Cheatsheets