AAAA requests are case sensative causing nxdoamin

[Dantzig, Brian]

I am running MaraDNS 1.2.12.08 as an authoratative name server and have
had problems with some customers sending me e-mail. I have done packet
captures that show the customer doing a AAAA request for MEDLINE.COM
which is answered with RCODE 03 (NXDOMAIN). I do not have IPv4 addresses
and the remote system also does a query for an MX record but the AAAA
query comes first. The remote mail system fails once it gets the
NXDOMAIN response. I have a zone file for my domain "medline.com" which
has an A record like 
    %  A  205.233.244.135

When I test with:
    dig @ns1.medline.net  medline.com AAAA
I get the expected NOERROR  with no resource returned.

When I use all caps:
    dig @ns1.medline.net MEDLINE.COM  AAAA
I get NXDOMAIN

I have tested with maradns 1.3.07.09 and it has not exibited this
behavior. I have sent this mail to the list for two reasons.
1.    To bring this to the attention of others who may run across this.
2.    To see if anyone has a suggested workaround.

I am planning on upgrading to v1.3.07.09 in the next couple of months so
I think I can live with this for now.

PS
I want to thank Sam for all of the work he has done to create and
maintain this fine software. It is unfortunate that many people have to
deal with organizations where it is easier to spend thousands of dollars
for software and pay hundreds or thousands per year for lousy support
than to cut a check to the developer to get something fixed or added.
Nobody said the world makes sense. Sam, I hope your customers/employeers
can see that you don't just have the right tools and skills, you have
the Right Stuff!

From:
Brian Dantzig
Senior Network Engineer
Medline Industries