this post was submitted on 19 Nov 2023
4 points (83.3% liked)
Home Networking
198 readers
1 users here now
A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.
Rules
- Please stay on topic.
- Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
- No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
- No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
- Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
- No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
- No affiliate links.
- No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Setting your www directly to an A / AAAA record is easier, but using NS records instead allow your IP to change as your host changes it as if DNS was setup directly with the hosting provider. Learned my lesson last time my host decided to change the IP my service was hosted on.
You can than have a subdomain like home. where you maintain your public IP and a wildcard *. CNAME redirect to home. so that you can use nginx to expose your services easier, such as homeassistant., nodered., plex., etc...