So for the longest time the way my internal network was setup is each device/server had it's own .loc domain. That's just how I originally did it many years ago. This turned out to go against convention and ideally I should do host.domain.loc where domain is just a name I pick for the whole network.
As a total side note, browsers over the years have gotten a bit more picky about wanting HTTPS, especially for forms. Makes sense, but for local stuff the warnings were getting kind of annoying. Could do self signed certs which I did for some stuff, but still have to deal with THAT warning now, although it's one-time per browser/session.
So..... to kill two birds with one stone, I converted my whole network to using a subdomain of a domain I own. But I went further, and also set up a wildcard cert and use DNS based validation, which was a pain to setup but I got it going. The local sub domain doesn't resolve to anything on the internet, but on my local home DNS server I have a zone for it, so it resolves to all my servers. But the way it's setup, I can still pass cert validation.
It's oddly satisfying seeing valid HTTPS certs for local stuff such as my dev server and password manager, and no longer seeing the annoying drop down warning in forms.