Help with dns-suffixed single word domains pihole + swag reverse proxy (solved)

Help docker
1

Hey there,

So basically atm i have dns entries in pihole (192.168.69.3) that match my externally facing domains which point at my reverse proxy (192.168.69.111) i.e blah.somedomain.com this works and skips reaching out while in the local network.

But i want to try out single word domains while in the local network for ease

i have configured my dhcp server on my router to have a suffix of somedomain.com

when i nslookup blah.somdomain.com it returns the same results as blah

C:\Users\phyzical-gaming>nslookup blah
Server:  pi.hole
Address:  192.168.69.3

Name:    blah.somedomain.com
Addresses:  2606:4700:3031::ac43:8e62
          2606:4700:3034::6815:4f35
          192.168.69.111


C:\Users\phyzical-gaming>nslookup blah.somedomain.com
Server:  pi.hole
Address:  192.168.69.3

Name:    blah.somedomain.com
Addresses:  2606:4700:3031::ac43:8e62
          2606:4700:3034::6815:4f35
          192.168.69.111

But for some reason when i try https://blah in any browser it doesnt seem to reach anything? am i wrong in my assumption that a browser would auto dns suffix like nslookup would?

or any tips to help understand why a dns-suffice isnt the way to go? thanks!

edit: ended up just being that i missed some dnsmaq settings in my router

3

Try http://blah instead of https, and make sure no browser add-on enforcing https. That will help remove certificate issues from the equation. Try different browsers too – I get different behaviour on Safari and Chrome when using hostnames. Sometimes I need the protocol and other times I need to specify domain name component or else it defaults to a search for the word.