[BUG] invalid JSON output (ADDITIONNAL SECTION parsed as target domain records)

[nil0x42]

dnsx version:

DNSX Version: 1.2.2

Current Behavior:

Some dns resolvers (e.g: 84.53.242.102) provide more than just ANSWER SECTION. Indeed, many resolvers provide AUTHORITY SECTION and ADDITIONAL SECTION.

Example:
$ dig @84.53.242.102 anyinvaliddomain.ticketing.cm.com

; <<>> DiG 9.20.16 <<>> @84.53.242.102 anyinvaliddomain.ticketing.cm.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62158
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13

;; QUESTION SECTION:
;anyinvaliddomain.ticketing.cm.com. IN	A

;; AUTHORITY SECTION:
.			79449	IN	NS	g.root-servers.net.
.			79449	IN	NS	h.root-servers.net.
.			79449	IN	NS	i.root-servers.net.
.			79449	IN	NS	j.root-servers.net.
.			79449	IN	NS	k.root-servers.net.
.			79449	IN	NS	l.root-servers.net.
.			79449	IN	NS	m.root-servers.net.
.			79449	IN	NS	a.root-servers.net.
.			79449	IN	NS	b.root-servers.net.
.			79449	IN	NS	c.root-servers.net.
.			79449	IN	NS	d.root-servers.net.
.			79449	IN	NS	e.root-servers.net.
.			79449	IN	NS	f.root-servers.net.

;; ADDITIONAL SECTION:
g.root-servers.net.	77741	IN	A	192.112.36.4
h.root-servers.net.	77741	IN	A	198.97.190.53
i.root-servers.net.	77741	IN	A	192.36.148.17
j.root-servers.net.	77741	IN	A	192.58.128.30
k.root-servers.net.	77741	IN	A	193.0.14.129
l.root-servers.net.	79739	IN	A	199.7.83.42
m.root-servers.net.	77741	IN	A	202.12.27.33
a.root-servers.net.	81186	IN	A	198.41.0.4
b.root-servers.net.	81186	IN	A	170.247.170.2
c.root-servers.net.	77741	IN	A	192.33.4.12
d.root-servers.net.	77741	IN	A	199.7.91.13
e.root-servers.net.	77741	IN	A	192.203.230.10
f.root-servers.net.	77741	IN	A	192.5.5.241

;; Query time: 258 msec
;; SERVER: 84.53.242.102#53(84.53.242.102) (UDP)
;; WHEN: Thu Dec 04 15:26:53 CET 2025
;; MSG SIZE  rcvd: 470

The problem with dnsx (and also its json output), si that it seems to parse records from EVERY section instead of just considering the ANSWER section (when available).

As a result, when automating subdomain resolutions, many false positive appear with IPs of root DNS servers (and sometimes others servers returned in ADDITIONAL SECTION) as if they were valid A records for the FQDN.

Expected Behavior:

Only records from ANSWER SECTION are considered. An alternative would consist in adding a json entry 'other_sections' to collect alternative section informations.

Steps To Reproduce:

1. Run echo anyinvaliddomain.ticketing.cm.com | dnsx -disable-update-check -silent -no-color -retry 1 -resolver 84.53.242.102 -stream -resp -a -cname -json -omit-raw | jq
2. Observe that root-servers a records have been added to json 'a' section at top of the tree,as if the domain resolved to these IPs:

{
  "host": "anyinvaliddomain.ticketing.cm.com",
  "ttl": 77076,
  "resolver": [
    "84.53.242.102:53"
  ],
  "a": [
    "192.203.230.10",
    "192.5.5.241",
    "192.112.36.4",
    "198.97.190.53",
    "192.36.148.17",
    "192.58.128.30",
    "193.0.14.129",
    "199.7.83.42",
    "202.12.27.33",
    "198.41.0.4",
    "170.247.170.2",
    "192.33.4.12",
    "199.7.91.13"
  ],
...

Anything else:

[nil0x42]

Note that this behavior also happens with simple output:

# echo anyinvaliddomain.ticketing.cm.com | dnsx -resolver 84.53.242.102 -resp -a -cname

      _             __  __
   __| | _ __   ___ \ \/ /
  / _' || '_ \ / __| \  /
 | (_| || | | |\__ \ /  \
  \__,_||_| |_||___//_/\_\

                projectdiscovery.io

[INF] Current dnsx version 1.2.2 (latest)
anyinvaliddomain.ticketing.cm.com [A] [202.12.27.33]
anyinvaliddomain.ticketing.cm.com [A] [198.41.0.4]
anyinvaliddomain.ticketing.cm.com [A] [170.247.170.2]
anyinvaliddomain.ticketing.cm.com [A] [192.33.4.12]
anyinvaliddomain.ticketing.cm.com [A] [199.7.91.13]
anyinvaliddomain.ticketing.cm.com [A] [192.203.230.10]
anyinvaliddomain.ticketing.cm.com [A] [192.5.5.241]
anyinvaliddomain.ticketing.cm.com [A] [192.112.36.4]
anyinvaliddomain.ticketing.cm.com [A] [198.97.190.53]
anyinvaliddomain.ticketing.cm.com [A] [192.36.148.17]
anyinvaliddomain.ticketing.cm.com [A] [192.58.128.30]
anyinvaliddomain.ticketing.cm.com [A] [193.0.14.129]
anyinvaliddomain.ticketing.cm.com [A] [199.7.83.42]

[dogancanbakir]

Thanks for letting us know! I've raised a PR here. When you have a moment, please check if it works on your end. Here's the link: 923 filter answer section only #926.

[nil0x42]

Hi ! It looks like the fix doesn't work properly.

Look at this:

~/dev/dnsx (923_filter_answer_section_only)$ dig @91.191.14.15 www.google.com

; <<>> DiG 9.20.16 <<>> @91.191.14.15 www.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49901
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;www.google.com.			IN	A

;; ANSWER SECTION:
www.google.com.		184	IN	A	142.251.39.4

;; AUTHORITY SECTION:
google.com.		91818	IN	NS	ns2.google.com.
google.com.		91818	IN	NS	ns1.google.com.
google.com.		91818	IN	NS	ns4.google.com.
google.com.		91818	IN	NS	ns3.google.com.

;; ADDITIONAL SECTION:
ns2.google.com.		191948	IN	A	216.239.34.10
ns1.google.com.		191948	IN	A	216.239.32.10
ns4.google.com.		191951	IN	A	216.239.38.10
ns3.google.com.		191951	IN	A	216.239.36.10

;; Query time: 107 msec
;; SERVER: 91.191.14.15#53(91.191.14.15) (UDP)
;; WHEN: Tue Dec 09 15:10:12 CET 2025
;; MSG SIZE  rcvd: 184

In this case, we expect to receive a single A record (in my case it is 142.251.39.4). But when i try with your patch, no records at all are retrieved:

~/dev/dnsx (923_filter_answer_section_only)$ echo www.google.com | go run ./cmd/dnsx -duc -silent -nc -retry 1 -resolver 91.191.14.15 -stream -resp -a -cname -raw -j | jq

{
  "host": "www.google.com",
  "ttl": 219,
  "resolver": [
    "91.191.14.15:53"
  ],
  "raw": ";; opcode: QUERY, status: NOERROR, id: 38592\n;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4\n\n;; QUESTION SECTION:\n;www.google.com.\tIN\t A\n\n;; ANSWER SECTION:\nwww.google.com.\t219\tIN\tA\t142.251.39.4\n\n;; AUTHORITY SECTION:\ngoogle.com.\t91853\tIN\tNS\tns1.google.com.\ngoogle.com.\t91853\tIN\tNS\tns4.google.com.\ngoogle.com.\t91853\tIN\tNS\tns3.google.com.\ngoogle.com.\t91853\tIN\tNS\tns2.google.com.\n\n;; ADDITIONAL SECTION:\nns1.google.com.\t191983\tIN\tA\t216.239.32.10\nns4.google.com.\t191986\tIN\tA\t216.239.38.10\nns3.google.com.\t191986\tIN\tA\t216.239.36.10\nns2.google.com.\t191983\tIN\tA\t216.239.34.10\n;; opcode: QUERY, status: NOERROR, id: 38592\n;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4\n\n;; QUESTION SECTION:\n;www.google.com.\tIN\t CNAME\n\n;; AUTHORITY SECTION:\ngoogle.com.\t91852\tIN\tNS\tns4.google.com.\ngoogle.com.\t91852\tIN\tNS\tns3.google.com.\ngoogle.com.\t91852\tIN\tNS\tns2.google.com.\ngoogle.com.\t91852\tIN\tNS\tns1.google.com.\n\n;; ADDITIONAL SECTION:\nns4.google.com.\t191985\tIN\tA\t216.239.38.10\nns3.google.com.\t191985\tIN\tA\t216.239.36.10\nns2.google.com.\t191982\tIN\tA\t216.239.34.10\nns1.google.com.\t191982\tIN\tA\t216.239.32.10\n",
  "status_code": "NOERROR",
  "raw_resp": {
    "Id": 38592,
    "Response": true,
    "Opcode": 0,
    "Authoritative": false,
    "Truncated": false,
    "RecursionDesired": true,
    "RecursionAvailable": true,
    "Zero": false,
    "AuthenticatedData": false,
    "CheckingDisabled": false,
    "Rcode": 0,
    "Question": [
      {
        "Name": "www.google.com.",
        "Qtype": 5,
        "Qclass": 1
      }
    ],
    "Answer": null,
    "Ns": [
      {
        "Hdr": {
          "Name": "google.com.",
          "Rrtype": 2,
          "Class": 1,
          "Ttl": 91852,
          "Rdlength": 6
        },
        "Ns": "ns4.google.com."
      },
      {
        "Hdr": {
          "Name": "google.com.",
          "Rrtype": 2,
          "Class": 1,
          "Ttl": 91852,
          "Rdlength": 6
        },
        "Ns": "ns3.google.com."
      },
      {
        "Hdr": {
          "Name": "google.com.",
          "Rrtype": 2,
          "Class": 1,
          "Ttl": 91852,
          "Rdlength": 6
        },
        "Ns": "ns2.google.com."
      },
      {
        "Hdr": {
          "Name": "google.com.",
          "Rrtype": 2,
          "Class": 1,
          "Ttl": 91852,
          "Rdlength": 6
        },
        "Ns": "ns1.google.com."
      }
    ],
    "Extra": [
      {
        "Hdr": {
          "Name": "ns4.google.com.",
          "Rrtype": 1,
          "Class": 1,
          "Ttl": 191985,
          "Rdlength": 4
        },
        "A": "216.239.38.10"
      },
      {
        "Hdr": {
          "Name": "ns3.google.com.",
          "Rrtype": 1,
          "Class": 1,
          "Ttl": 191985,
          "Rdlength": 4
        },
        "A": "216.239.36.10"
      },
      {
        "Hdr": {
          "Name": "ns2.google.com.",
          "Rrtype": 1,
          "Class": 1,
          "Ttl": 191982,
          "Rdlength": 4
        },
        "A": "216.239.34.10"
      },
      {
        "Hdr": {
          "Name": "ns1.google.com.",
          "Rrtype": 1,
          "Class": 1,
          "Ttl": 191982,
          "Rdlength": 4
        },
        "A": "216.239.32.10"
      }
    ]
  },
  "timestamp": "2025-12-09T15:09:38.468749999+01:00"
}

And the "raw" json entry shows that the ANSWER SECTION has been correctly received by dnsx, so the single real A record sould appear in json's "a"

[nil0x42]

Here is another tricky case:
echo emph.sharepoint.com | dnsx -disable-update-check -silent -no-color -retry 1 -resolver 178.33.164.91 -stream -resp -a -cname -json -raw | jq

{
  "host": "emph.sharepoint.com",
  "ttl": 2585,
  "resolver": [
    "178.33.164.91:53"
  ],
  "a": [
    "13.107.136.10",
    "13.107.138.10",
    "13.107.136.1",
    "13.107.136.2",
    "13.107.138.1",
    "13.107.138.2",
    "13.107.236.221"
  ],
  "aaaa": [
    "2603:1061:0:700::dd"
  ],
  "cname": [
    "13777-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com",
    "189376-ipv4v6e.farm.dprodmgd104.aa-rt.sharepoint.com",
    "189376-ipv4v6e.farm.dprodmgd104.sharepointonline.com.akadns.net",
    "189376-ipv4v6.farm.dprodmgd104.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net",
    "dual-spo-0005.spo-msedge.net"
  ],
  "ns": [
    "ns2.spo-msedge.net",
    "ns1.spo-msedge.net",
    "ns3.spo-msedge.net",
    "ns4.spo-msedge.net",
    "ns1-221.azure-dns.com",
    "ns2-221.azure-dns.net",
    "ns4-221.azure-dns.info",
    "ns3-221.azure-dns.org"
  ],
  "all": [
    "emph.sharepoint.com.\t2585\tIN\tCNAME\t13777-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com.",
    "13777-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com.\t60\tIN\tCNAME\t189376-ipv4v6e.farm.dprodmgd104.aa-rt.sharepoint.com.",
    "189376-ipv4v6e.farm.dprodmgd104.aa-rt.sharepoint.com.\t60\tIN\tCNAME\t189376-ipv4v6e.farm.dprodmgd104.sharepointonline.com.akadns.net.",
    "189376-ipv4v6e.farm.dprodmgd104.sharepointonline.com.akadns.net.\t300\tIN\tCNAME\t189376-ipv4v6.farm.dprodmgd104.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net.",
    "189376-ipv4v6.farm.dprodmgd104.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net.\t240\tIN\tCNAME\tdual-spo-0005.spo-msedge.net.",
    "dual-spo-0005.spo-msedge.net.\t240\tIN\tA\t13.107.136.10",
    "dual-spo-0005.spo-msedge.net.\t240\tIN\tA\t13.107.138.10",
    "ns1.spo-msedge.net.\t170410\tIN\tA\t13.107.136.1",
    "ns2.spo-msedge.net.\t170410\tIN\tA\t13.107.136.2",
    "ns3.spo-msedge.net.\t170410\tIN\tA\t13.107.138.1",
    "ns4.spo-msedge.net.\t170410\tIN\tA\t13.107.138.2",
    "\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags:; udp: 1232",
    "spo-msedge.net.\t170410\tIN\tNS\tns2.spo-msedge.net.",
    "spo-msedge.net.\t170410\tIN\tNS\tns1.spo-msedge.net.",
    "spo-msedge.net.\t170410\tIN\tNS\tns3.spo-msedge.net.",
    "spo-msedge.net.\t170410\tIN\tNS\tns4.spo-msedge.net.",
    "ns1-221.azure-dns.com.\t7257\tIN\tA\t13.107.236.221",
    "ns1-221.azure-dns.com.\t7257\tIN\tAAAA\t2603:1061:0:700::dd",
    "sharepoint.com.\t7257\tIN\tNS\tns1-221.azure-dns.com.",
    "sharepoint.com.\t7257\tIN\tNS\tns2-221.azure-dns.net.",
    "sharepoint.com.\t7257\tIN\tNS\tns4-221.azure-dns.info.",
    "sharepoint.com.\t7257\tIN\tNS\tns3-221.azure-dns.org."
  ],
  "raw": ";; opcode: QUERY, status: NOERROR, id: 38412\n;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 4, ADDITIONAL: 5\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags:; udp: 1232\n\n;; QUESTION SECTION:\n;emph.sharepoint.com.\tIN\t A\n\n;; ANSWER SECTION:\nemph.sharepoint.com.\t2585\tIN\tCNAME\t13777-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com.\n13777-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com.\t60\tIN\tCNAME\t189376-ipv4v6e.farm.dprodmgd104.aa-rt.sharepoint.com.\n189376-ipv4v6e.farm.dprodmgd104.aa-rt.sharepoint.com.\t60\tIN\tCNAME\t189376-ipv4v6e.farm.dprodmgd104.sharepointonline.com.akadns.net.\n189376-ipv4v6e.farm.dprodmgd104.sharepointonline.com.akadns.net.\t300\tIN\tCNAME\t189376-ipv4v6.farm.dprodmgd104.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net.\n189376-ipv4v6.farm.dprodmgd104.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net.\t240\tIN\tCNAME\tdual-spo-0005.spo-msedge.net.\ndual-spo-0005.spo-msedge.net.\t240\tIN\tA\t13.107.136.10\ndual-spo-0005.spo-msedge.net.\t240\tIN\tA\t13.107.138.10\n\n;; AUTHORITY SECTION:\nspo-msedge.net.\t170410\tIN\tNS\tns2.spo-msedge.net.\nspo-msedge.net.\t170410\tIN\tNS\tns1.spo-msedge.net.\nspo-msedge.net.\t170410\tIN\tNS\tns3.spo-msedge.net.\nspo-msedge.net.\t170410\tIN\tNS\tns4.spo-msedge.net.\n\n;; ADDITIONAL SECTION:\nns1.spo-msedge.net.\t170410\tIN\tA\t13.107.136.1\nns2.spo-msedge.net.\t170410\tIN\tA\t13.107.136.2\nns3.spo-msedge.net.\t170410\tIN\tA\t13.107.138.1\nns4.spo-msedge.net.\t170410\tIN\tA\t13.107.138.2\n;; opcode: QUERY, status: NOERROR, id: 38412\n;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 3\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags:; udp: 1232\n\n;; QUESTION SECTION:\n;emph.sharepoint.com.\tIN\t CNAME\n\n;; ANSWER SECTION:\nemph.sharepoint.com.\t2585\tIN\tCNAME\t13777-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com.\n\n;; AUTHORITY SECTION:\nsharepoint.com.\t7257\tIN\tNS\tns1-221.azure-dns.com.\nsharepoint.com.\t7257\tIN\tNS\tns2-221.azure-dns.net.\nsharepoint.com.\t7257\tIN\tNS\tns4-221.azure-dns.info.\nsharepoint.com.\t7257\tIN\tNS\tns3-221.azure-dns.org.\n\n;; ADDITIONAL SECTION:\nns1-221.azure-dns.com.\t7257\tIN\tA\t13.107.236.221\nns1-221.azure-dns.com.\t7257\tIN\tAAAA\t2603:1061:0:700::dd\n",
  "status_code": "NOERROR",
  "raw_resp": {
    "Id": 38412,
    "Response": true,
    "Opcode": 0,
    "Authoritative": false,
    "Truncated": false,
    "RecursionDesired": true,
    "RecursionAvailable": true,
    "Zero": false,
    "AuthenticatedData": false,
    "CheckingDisabled": false,
    "Rcode": 0,
    "Question": [
      {
        "Name": "emph.sharepoint.com.",
        "Qtype": 5,
        "Qclass": 1
      }
    ],
    "Answer": [
      {
        "Hdr": {
          "Name": "emph.sharepoint.com.",
          "Rrtype": 5,
          "Class": 1,
          "Ttl": 2585,
          "Rdlength": 40
        },
        "Target": "13777-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com."
      }
    ],
    "Ns": [
      {
        "Hdr": {
          "Name": "sharepoint.com.",
          "Rrtype": 2,
          "Class": 1,
          "Ttl": 7257,
          "Rdlength": 20
        },
        "Ns": "ns1-221.azure-dns.com."
      },
      {
        "Hdr": {
          "Name": "sharepoint.com.",
          "Rrtype": 2,
          "Class": 1,
          "Ttl": 7257,
          "Rdlength": 23
        },
        "Ns": "ns2-221.azure-dns.net."
      },
      {
        "Hdr": {
          "Name": "sharepoint.com.",
          "Rrtype": 2,
          "Class": 1,
          "Ttl": 7257,
          "Rdlength": 24
        },
        "Ns": "ns4-221.azure-dns.info."
      },
      {
        "Hdr": {
          "Name": "sharepoint.com.",
          "Rrtype": 2,
          "Class": 1,
          "Ttl": 7257,
          "Rdlength": 23
        },
        "Ns": "ns3-221.azure-dns.org."
      }
    ],
    "Extra": [
      {
        "Hdr": {
          "Name": "ns1-221.azure-dns.com.",
          "Rrtype": 1,
          "Class": 1,
          "Ttl": 7257,
          "Rdlength": 4
        },
        "A": "13.107.236.221"
      },
      {
        "Hdr": {
          "Name": "ns1-221.azure-dns.com.",
          "Rrtype": 28,
          "Class": 1,
          "Ttl": 7257,
          "Rdlength": 16
        },
        "AAAA": "2603:1061:0:700::dd"
      },
      {
        "Hdr": {
          "Name": ".",
          "Rrtype": 41,
          "Class": 1232,
          "Ttl": 0,
          "Rdlength": 0
        },
        "Option": null
      }
    ]
  },
  "timestamp": "2025-12-09T16:53:28.413366527+01:00"
}

Here, we only want 13.107.138.10 and 13.107.136.10 in A records.
dig output for the record:
dig @178.33.164.91 emph.sharepoint.com

; <<>> DiG 9.20.16 <<>> @178.33.164.91 emph.sharepoint.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51968
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 4, ADDITIONAL: 5

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 10da61d12a40373f154c453869384380cab310228bfd98b2 (good)
;; QUESTION SECTION:
;emph.sharepoint.com.		IN	A

;; ANSWER SECTION:
emph.sharepoint.com.	3214	IN	CNAME	13777-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com.
13777-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com. 60 IN CNAME 189376-ipv4v6e.farm.dprodmgd104.aa-rt.sharepoint.com.
189376-ipv4v6e.farm.dprodmgd104.aa-rt.sharepoint.com. 60 IN CNAME 189376-ipv4v6e.farm.dprodmgd104.sharepointonline.com.akadns.net.
189376-ipv4v6e.farm.dprodmgd104.sharepointonline.com.akadns.net. 212 IN	CNAME 189376-ipv4v6g.farm.dprodmgd104.sharepointonline.com.akadns.net.
189376-ipv4v6g.farm.dprodmgd104.sharepointonline.com.akadns.net. 300 IN	CNAME 189376-ipv4v6.farm.dprodmgd104.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net.
189376-ipv4v6.farm.dprodmgd104.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net. 152 IN CNAME dual-spo-0005.spo-msedge.net.
dual-spo-0005.spo-msedge.net. 152 IN	A	13.107.138.10
dual-spo-0005.spo-msedge.net. 152 IN	A	13.107.136.10

;; AUTHORITY SECTION:
spo-msedge.net.		171039	IN	NS	ns2.spo-msedge.net.
spo-msedge.net.		171039	IN	NS	ns3.spo-msedge.net.
spo-msedge.net.		171039	IN	NS	ns4.spo-msedge.net.
spo-msedge.net.		171039	IN	NS	ns1.spo-msedge.net.

;; ADDITIONAL SECTION:
ns1.spo-msedge.net.	171039	IN	A	13.107.136.1
ns2.spo-msedge.net.	171039	IN	A	13.107.136.2
ns3.spo-msedge.net.	171039	IN	A	13.107.138.1
ns4.spo-msedge.net.	171039	IN	A	13.107.138.2

;; Query time: 119 msec
;; SERVER: 178.33.164.91#53(178.33.164.91) (UDP)
;; WHEN: Tue Dec 09 16:42:59 CET 2025
;; MSG SIZE  rcvd: 541