Differences

This shows you the differences between two versions of the page.

--- pages:howtos:diagnose:how-to-diagnose-dns-with-dig [2024/05/07 13:00] – [Determine the DNS Server holding a RDNS (PTR) Record] mischerh
+++ pages:howtos:diagnose:how-to-diagnose-dns-with-dig [2024/05/07 13:30] (current) – [How to interpret DIG output] mischerh
@@ Line 14: / Line 14: @@
   * @a.ns14.net: specifying the DNS server to query
   * nanoscopic.de: the name to query for
+If no type is specified, dig queries for an "A"-record. If not told to query a specific name server, dig will try each of the servers listed in the systems /etc/resolv.conf. Have a look at the [[https://linux.die.net/man/1/dig | dig manual page]] for more options.
+<sxh bash; gutter: false>
+dig wiretrip.de
+</sxh>
+<code>
+; <<>> DiG 9.18.26 <<>> wiretrip.de
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43783
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
+;; OPT PSEUDOSECTION:
+; EDNS: version: 0, flags:; udp: 1424
+;; QUESTION SECTION:
+;wiretrip.de.                   IN      A
+;; ANSWER SECTION:
+wiretrip.de.            3600    IN      A       159.69.16.204
+;; Query time: 13 msec
+;; SERVER: 192.168.1.1#53(192.168.1.1) (UDP)
+;; WHEN: Tue May 07 15:18:42 CEST 2024
+;; MSG SIZE  rcvd: 56
+</code>
@@ Line 130: / Line 157: @@
-For IPv6 addresses, e.g. 2003:a:b1c:f420:be24:11ff:feb3:a94f, replace the last four hexadecimal digits with a zero 2003:a:b1c:f420:be24:11ff:feb3:0.
+For IPv6 addresses, e.g. 2003:a:b1c:f420:be24:11ff:feb3:a94f, replace the last four hexadecimal digits with a zero: 2003:a:b1c:f420:be24:11ff:feb3:0.
-===== Query the RDNS server of a Network Segment for current data =====
+===== Query the RDNS server of a Network Segment for current PTR data =====
 To get current RDNS data, use @<HOSTNAME_OF_RDNS_SERVER>.
@@ Line 163: / Line 190: @@
 </code>
+===== How to inspect a SPF Record =====
-===== How to interpret DIG output =====
+Determine the authoritative DNS server
+<sxh bash; gutter: false>
+dig -t SOA mx.wiretrip.de
+</sxh>
+<code>
+; <<>> DiG 9.18.26 <<>> -t soa wiretrip.de
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58644
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
+;; OPT PSEUDOSECTION:
+; EDNS: version: 0, flags:; udp: 1424
+;; QUESTION SECTION:
+;wiretrip.de.                   IN      SOA
+;; ANSWER SECTION:
+wiretrip.de.            43200   IN      SOA     a.ns14.net. domains.wiretrip.de. 2024050305 43200 14400 604800 43200
+;; Query time: 139 msec
+;; SERVER: 192.168.1.1#53(192.168.1.1) (UDP)
+;; WHEN: Tue May 07 15:08:24 CEST 2024
+;; MSG SIZE  rcvd: 94
+</code>
+Then query the authoritative DNS server for current data:
+<sxh bash; gutter: false>
+dig @a.ns14.net -t TXT wiretrip.de
+</sxh>
+<code>
+; <<>> DiG 9.18.26 <<>> @a.ns14.net -t TXT wiretrip.de
+; (2 servers found)
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48047
+;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
+;; WARNING: recursion requested but not available
+;; OPT PSEUDOSECTION:
+; EDNS: version: 0, flags:; udp: 1232
+;; QUESTION SECTION:
+;wiretrip.de.                   IN      TXT
+;; ANSWER SECTION:
+wiretrip.de.            43200   IN      TXT     "v=spf1 ip4:159.69.16.204 ip4:80.147.157.18 ip6:2a01:4f8:c0c:fa5c::1 ip6:2003:a:b1c:f420:f0ce:b1ff:fe08:3162 -all"
+wiretrip.de.            43200   IN      TXT     "YweIdum3Gyt2qOzYU44Q"
+;; Query time: 16 msec
+;; SERVER: 62.116.159.231#53(a.ns14.net) (UDP)
+;; WHEN: Tue May 07 15:09:38 CEST 2024
+;; MSG SIZE  rcvd: 198
+</code>
+<sxh bash; gutter: false>
+dig @a.ns14.net -t TXT wiretrip.de | grep spf
+</sxh>
+<code>
+wiretrip.de.            43200   IN      TXT     "v=spf1 ip4:159.69.16.204 ip4:80.147.157.18 ip6:2a01:4f8:c0c:fa5c::1 ip6:2003:a:b1c:f420:f0ce:b1ff:fe08:3162 -all"
+</code>
+===== How to interpret DIG output =====
+FIXME
+  * https://ns1.com/blog/decoding-dig-output
 ----
 ~~DISCUSSION~~