Bind9.11.20: nslookup shows different MX information on Windows and Linux workstation

[Wibble2004]

My dns server uses BIND 9.11.20-RedHat-9.11.20-5.el8, hosted on CentOS8:

/etc/named.conf:

$TTL 3H
@ IN SOA ns1.example.com. admin.example.com.(
1 ; serial
1D ; refresh
1H ; retry
1W ; expire
3H ) ; minimum
NS ns1.example.com.
NS ns3.example.com.
A 192.168.1.10
MX 10 mxa.other.com.
MX 10 mxb.other.com.
When I query MX records through nslookup, I found Windows and Linux show different information:

On Linux workstation(CentOS8):

nslookup
>server 10.0.0.204
> set type=MX
> example.com
Server: 10.0.0.204
Address: 10.0.0.204#53

example.com mail exchanger = 10 mxb.other.com.
example.com mail exchanger = 10 mxa.other.com.

On Windows(Win2019)

nslookup:
>server 10.0.0.204
> set type=MX
> example.com
Server: [10.0.0.204]
Address: 10.0.0.204

example.com MX preference = 10, mail exchanger = mxb.other.com
example.com MX preference = 10, mail exchanger = mxa.other.com
example.com nameserver = ns1.example.com
example.com nameserver = ns2.example.com
ns1.example.com internet address = 10.0.0.204
ns2.example.com internet address = 10.0.0.205

You may notice the following extra information showed on Windows 2019 nslookup output:

example.com nameserver = ns1.example.com
example.com nameserver = ns2.example.com
ns1.example.com internet address = 10.0.0.204
ns2.example.com internet address = 10.0.0.205

Should such extra information be a concern? or any bind configuration I should add to remove such information from windows nslookup output? thank you