400 bad request on http admin page when using DNS resolved name
I have an EAP245. I recently added a EAP225. Right now they are entirely seperate. No controller.
I use dnsmasq as my local DNS/DHCP server. Both EAP are setup to request an IP address via DHCP. Dnsmasq issues the "DHCP response" and also assigns a local DNS name.
'tl-eap245' resolves to 192.168.3.2. 'tl-eap225' resolves to 192.168.3.3
If I try to open 'http://tl-eap245' in either Chrome or Firefox (Windows 11) I get "400 bad request". I have to use "http://192.168.3.3".
My EAP-225 came shipped with EAP225(US)_V3_2.6.1 and I was able to use "http://tl-eap225" to open the admin page. However after updating the firmware to 5.1.0 Build 20220926 it now also reports "400 bad request" if I try to use the DNS name.
Is the above the end-of-the world, no. Clearly I can just use IP address but it's more convenient when I forget which EAP has which address if I can just use the DNS names.
Note this has nothing to do with the "tplinkeap.net" dynamic configuration domain, I am not using that. I tried to ask the above Q to tech support but they just couldn't grasp the concept that I managed my own DNS and wanted me to send them screenshots of my DNS. They kept referring to 'tplinkeap.net'. In the end I gave up trying to resolve it via them.