.VA tld has been intermittently wildcarded?

[Stephane Bortzmeyer]

On Sat, Nov 30, 2024 at 08:16:19PM -0500,
 Mark E. Jeftovic <markjr at easydns.com> wrote 
 a message of 133 lines which said:

> Our domainsure monitors started picking up some weirdness out of .va tld
> today as it appeared that up to 3 of their 5 nameservers were wildcarded and
> handing out NS records that seemed autogenerated:

Testing with RIPE Atlas probes, I confirm. Indeed, it seems only when
querying over IPv4:

% blaeu-resolve --requested 100 -4 --nameserver a.nic.va --authority --type NS --nsid ddfgdfgsdfgsdfg77567.va
Nameserver a.nic.va
Authority section of the DNS responses
[NSID: None; ck02-5a579ebef0-2d862c94.va.] : 1 occurrences 
[NSID: None; ck02-a1a1b9c5c5-5775dba3.va.] : 1 occurrences 
[NSID: None; ck02-e873380d46-c88e7f01.va.] : 1 occurrences 
[NSID: None; ck02-e25d66198a-c0913834.va.] : 1 occurrences 
...
[NSID: None; ck02-b41e40b8fc-57fb1f95.va.] : 1 occurrences 
[NSID: None; ck02-9b5f158a84-b91c6ca3.va.] : 1 occurrences 
[NSID: None; ck02-6c2a638a84-b923ebf9.va.] : 1 occurrences 
Test #83417305 done at 2024-12-01T08:51:00Z

Don't waste time writing to the managers. The address in the IANA
database returns an error message saying it does not exist and the one
in the SOA replies "Over quota".