@almirsahbaz
Ahhhhhh - now that make sense for me. Thanks for clearing things up. Back to your problem:
It will get troublesome....
PEAP Authentication "normally" requires the authenticator (aka the Server, Wifi Controller... some referring to it as a RADIUS-Server - which can also be a "role" performed by another server; often used are Domaincontrollers ) to offer a certificate. Simple speaking: Kind of similar to webserver-authentication for https.
Your phone then "checks" the provided certificate on validity. This validation step was "skipped". Skipping isn't supported anymore. This started already with android 11 (depending on oem-implementations).
So your Admins will have to deploy certificates as mentioned above and provide them to you.
The "domain" field you are mentioning is used to select the certificate of the authenticator (for a user it is often easier to enter the proper name then select the certificate out of the certificate store an the device).
The thing for you is:
You can't do anything, as your admins will have to think about the whole process. So you won't be able to use the hotspots until there have been some changes made by the admins.
What you can do is to inform the admins on the changes that google made starting at Android 11
The Android 11 update will break connecting to certain enterprise WiFi networks. Here's why and what you can do to fix it.
www.xda-developers.com
If they want to use PEAP further on with devices running Android 12, they will have to change something!