Internal DNS lookup troubles
Hi everyone just started and this is having fun.
Adjacent to homarr, but more about internal DNS lookup.
* I tried making an A record homarr.homelab.org pointing an internal IP
* making a SRV record pointing port 3000
* https or http //homarr.homelab.org does not work
* homarr.homelab.org:3000
* I did something similar for my other devices, synology.homelab.org - doesn't need a port number redirect
Is this because some sites are https or http and dont have redirect to https? right now i'm trying to sort out internal traffic before I even set up a secure reverse proxy
Thanks all
4 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
My A record and SRV record in my router DNS server
take this for what it's worth, how I approached my setup.
-- running pihole as internal DNS - so that's where I put my DNS entries
-- i use NGINX Proxy Manager (NPM) for internal and external forwarding
-- homer.loco is a local DNS entry that points my server running NPM
-- when NPM gets a request for homer.loco, it proxy's the connection to my other http[:]//server:3000
that way, if I have to get on my wife's machine or one of my kids, i just need to remember homer.loco instead of which server/port i put it up with
it will also help you start learning the reverse proxy side.
Oh thanks bud, gonna set up npm. I dabbled with npm before but it went over my head. I’m going to take baby steps