BUG: domain names - upper vs lower case

OS 6.5.0/6.5.1 (and many earlier versions)

(NOTE:  I'm currently dealing with netgear on a completely different problem which is preventing me from rebooting my NAS or doing anything that would cause any interruption in network traffic.  This process will probably take another 24-36 hours to run.  So, "try to reboot" isn't helpful.  Even if it would reverse what I'm describing below, it still leaves the BUG that the issue keeps popping up.)

(Another NOTE:  Netgear employees, please don't reply to this thread with a canned "welcome to the forum, to get started, do you have a backup made, what version are you running, etc" message.  What's needed is one of your engineers proficient in samba and ADS to look at the problem and fix it for ALL users.)

I've been using readynas products for many years with a windows domain (active directory) and there's one problem that keeps cropping up over and over.  Sometimes I don't see it for years, but it always eventually comes back:

The NAS names home directories based on the domain name.  For example, if my domain is "mydomain", then I can expect, on XRAID2, that the home directory for "garyd9" will be located at /data/home/mydomain/garyd9.  The problem is... sometimes it changes.  Sometimes, for a reason that I've never been able to understand, the NAS will boot and instead of using "mydomain", it will want to use MYDOMAIN.  For windows (which is case insensitive), this doesn't matter.  For the NAS (which uses case-sensitive linux file systems), this causes breakage.

Real Example: (actual domain and user names changed to protect my illusion of privacy.)

Today, I noticed that every single file in my home directory disappeared.  "Oh, no", I cry.  It'll take hours to pull that data back from my backup.  First, though, I go into the admin web interface and try to see what might have happened.. so I pop into the web interface, click shares, click browse, and start browsing the "home" subdirectories.  What I find is that my files are still there, exactly where they should be:  /data/home/mydomain/garyd9.  But, when I browse from windows, it's an empty folder.  Out of curiousity, I create a new file in my "home" share from windows.  That file does NOT show up in /data/home/mydomain/garyd9 when viewed from the web admin interface.

However, it DOES show up in /data/home/MYDOMAIN/garyd9.  

So, basically, the NAS today decided that I didn't need the files I had stored in mydomain/garyd9, and that it'd change it's interpretation of life to use the all CAPS "MYDOMAIN", which effectively granted me a brand new home share with nothing in it.

THIS IS BAD.  THIS IS VERY BAD.  This isn't the first time it's happened to me, either.  Here's a thread from a year ago when I had a similar situation:  https://community.netgear.com/t5/ReadyNAS-in-Business/quot-home-quot-directories-are-all-messed-up-how-to-just-wipe/m-p/965973

In that case, I didn't really push for Netgear to resolve the core problem - I just wanted help to work around it - which is a good thing because netgear apparently decided to completely ignore the core problem of the domain being renamed.  (Yes, in linux, changing the case of a string is RENAMING IT.)

So.. netgear.. If you are unable or unwilling to resolve the core issue, here's a REALLY simple "solution" to the problem:  Always force the domain name when used with the %D substitution to all upper case.  (or, all lower case.)  Being that Active Directory relies on DNS to function, and that DNS is case insensitive, this SHOULD work 100% of the time.  (You do compile a modified version of samba, right?)