Missing additional info for wildcard records

[EchoStone1101]

What happened:

When a wildcard record that triggers additional section processing is found, the additional section is not populated by the file plugin.

How to reproduce it (as minimally and precisely as possible):

Using the following zone file (j.txt):

j.		    500 IN SOA	    mname.com. rname.com. 3 604800 86400 2419200 604800
j.		    500 IN NS	    j.
j.		    500 IN A	    240.132.119.98
*.j.		500 IN MX	    10 j.

and this Corefile:

j.:1053 {
    header {
        response set ra
    }
    file j.txt
}

Response for querying <a.j., MX> (output beautified):

root@e10adfbeed3f:/v# dig @127.0.0.1 -p 1053 a.j. MX 

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16373
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;a.j.                           IN      MX

;; ANSWER SECTION:
a.j.                    500     IN      MX      10 j.

;; AUTHORITY SECTION:
j.                      500     IN      NS      j.

What you expected to happen:

The ADDITIONAL section should include the j. A record because it is relevant to *.j. MX j..

Anything else we need to know?:

Environment:

• the version of CoreDNS: CoreDNS-1.11.1, linux/arm64, go1.21.5, 45923b6e
• Corefile: given above.
• OS: this uses the docker environment from "Compilation with Docker".
• Others:

Bind9 correctly populates the ADDITIONAL section under the same setup. Also, in CoreDNS, the additional section is populated when querying specifically for <*.j., MX>.