Home Networking

189 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 10 months ago

MODERATORS

[email protected]

Why pay over $100.00 for dynamic dns services. (alien.top)

submitted 10 months ago by [email protected] to c/[email protected]

18 comments fedilink hide all child comments

Why would persons pay no-ip and others over $9.0/ month for dynamic dns. When you own your own domain is beyong me. Even worst, you purchased your domain with the likes no-ip.com, and others. They still want you to pay!!

Help me understand the logics.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 10 months ago (2 children)

I can ask the same about wildcard DNS. Even if you are willing to setup a docker container to keep your DNS updated no matter where it is hosted, normally you can only do so with one domain at a time. Want wildcard redirects? Most providers make you switch over to a virtual dedicated hosting. Thankfully cloudflare exists. You have full control over DNS, it’s free and they allow you to set www subdomain to a nameserver of your hosting provider and use dns trickery to cname the root domain to www, leaving all of the other subdomains free for you to use as you please.

[–] [email protected] 0 points 10 months ago (1 children)

Ok will check for more infor.

[–] [email protected] 0 points 10 months ago

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...