Phone or walk up to helpdesk, they open one for you.

deleted by creator

I have a domain registered that I use, just didn’t feel the need to mention it exactly. Hence why I anonymized my results. I did not change anything that would alter the troubleshooting steps, only the domain name and ip addresses are generic but otherwise consistent.

The domain and records are set up correctly on the provider end because I receive valid let’s encrypt certs for my subdomains through caddy. The issue is only with Fedora. I checked a live of ubuntu and fedora iso on a second computer. Fedora consistently cannot resolve the domains on the default configuration while ubuntu and anything else I tried can.

I just tried adding the local IP:Port and the app.domain.example to the /etc/hosts file as the examples show. Restarted systemd-resolved but no dice. Ideally, I’d like to make this family friendly and avoid having to make client specific configurations anyway. So far only I run fedora at home, so my device has this issue only. I am partial to the OS otherwise, so I was hoping I could solve this.

EDIT Sorry about that it dawned on my what you asked for really. From the resolvedctl results DNS Domain: domain.local would be mydomainname.local. Yes I kept .local in the search domain fields for most of my things. Is this something that matters, or could this be a workaround if I changed it to my actual mydomainname.tld? As far as I undertand this would work if mDNS was on. Not sure if LLMNR makes use of it the same way.