On 2025-05-20 at 14:38:40 UTC-0400 (Tue, 20 May 2025 18:38:40 +0000)
Rupert Gallagher <r...@protonmail.com>
is rumored to have said:
I wonder how it works for real, since mailspike.net itself fails DNS
resolution.
Not so.
$ dig mailspike.net NS
; <<>> DiG 9.10.6 <<>> mailspike.net NS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53129
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 4
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mailspike.net. IN NS
;; ANSWER SECTION:
mailspike.net. 10996 IN NS ns11.mailspike.net.
mailspike.net. 10996 IN NS ns13.mailspike.net.
mailspike.net. 10996 IN NS ns12.mailspike.net.
;; ADDITIONAL SECTION:
ns11.mailspike.net. 10996 IN A 185.175.91.11
ns12.mailspike.net. 10996 IN A 185.175.91.12
ns13.mailspike.net. 10996 IN A 185.175.91.13
;; Query time: 12 msec
;; SERVER: 192.168.254.111#53(192.168.254.111)
;; WHEN: Wed May 21 08:29:44 EDT 2025
;; MSG SIZE rcvd: 147
There is no need for any domain to have an A record for resolutions of
hosts and subdomains to resolve correctly. It is the NS record that
matters.
On Tuesday, May 20th, 2025 at 6:57 PM, Reindl Harald (privat)
<ha...@rhsoft.net> wrote:
[SNIP]
Ignore "Harry," who has been banned from the list but continues to
respond by direct mail to posters privately in his inimitable
aggressively incorrect style.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo@toad.social and many *@billmail.scconsult.com
addresses)
Not Currently Available For Hire
