Consider the domain outlouk.com (yes, there is a typo in that domain name). It’s a parked domain whose name servers, ns{1,2}.parkingcrew.net, seem to be rather buggy. For instance, these name servers will return TXT records of class IN in reply to a TXT query regardless of the query class.
This, however, exhibits an issue in Zonemaster and especially in the Nameserver15 test case: when I run a test on outlouk.com, it assumes that the name servers will return resource records that match the query class.
Example of the name server returning IN TXT records in response to a CH TXT query:
$ dig +nord @ns1.parkingcrew.net CH TXT version.bind
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.18.11 <<>> +nord @ns1.parkingcrew.net CH TXT version.bind
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10512
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;version.bind. CH TXT
;; ANSWER SECTION:
version.bind. 3600 IN TXT "v=spf1 -all"
;; Query time: 19 msec
;; SERVER: 13.248.158.159#53(ns1.parkingcrew.net) (UDP)
;; WHEN: Wed Sep 13 08:32:07 CEST 2023
;; MSG SIZE rcvd: 66
And Nameserver15 erroneously reporting that the name servers give v=spf1 -all as version strings:
$ zonemaster-cli --test NAMESERVER/nameserver15 --level INFO outlouk.com
Seconds Level Message
======= ========= =======
0.00 INFO Using version v4.6.2 of the Zonemaster engine.
1.67 INFO The following name server(s) respond to software version query "version.bind" with string "v=spf1 -all". Returned from name servers: "ns1.parkingcrew.net/13.248.158.159;ns2.parkingcrew.net/76.223.21.9"
1.67 INFO The following name server(s) respond to software version query "version.server" with string "v=spf1 -all". Returned from name servers: "ns1.parkingcrew.net/13.248.158.159;ns2.parkingcrew.net/76.223.21.9"
Consider the domain outlouk.com (yes, there is a typo in that domain name). It’s a parked domain whose name servers, ns{1,2}.parkingcrew.net, seem to be rather buggy. For instance, these name servers will return TXT records of class IN in reply to a TXT query regardless of the query class.
This, however, exhibits an issue in Zonemaster and especially in the Nameserver15 test case: when I run a test on outlouk.com, it assumes that the name servers will return resource records that match the query class.
Example of the name server returning IN TXT records in response to a CH TXT query:
And Nameserver15 erroneously reporting that the name servers give
v=spf1 -allas version strings: