What to do after getting a domain name?
2026-06-11 03:09 UTC
Replies (8)
-
@helix@feddit.org 2026-06-11 04:47
Don’t run services like these on a free domain. Get a very cheap domain from almost any provider. These free ones often try to get you to buy their domain name for outrageous prices with tricks and footnotes.
-
@Cyber@feddit.uk 2026-06-11 06:21
Kinda overlapping other replies, but to answer your question: A = your external IPv4 address The rest could be empty AAAA = an external IPv6 address NS = a DNS server MX = Mail Server TXT is just text, but it can be used by, ie Lets Encrypt to prove you own that domain for your SSL certificate If you open TCP 80 / 443 on the open internet EVERYONE will probe you, but you want to run a Friendica server, so you kinda need that (disclaimer: I do not know how Friendica is setup) So, you’ll need something (firewall, Fail2Ban, etc) to protect your server whilst also allowing it to federate to other servers. I’d strongely suggest you put your server on a VPS with a provider that has some level of defense already setup for you. I wouldn’t run this in your home network with putting it into a DMZ of some kind.
-
@lemmyvore@feddit.nl 2026-06-11 09:53
First of all I would suggest getting your own domain. There's many TLDs and ccTLDs that will let you get a domain for $10/year or much less. If you don't want to pay then at least get a subdomain from somewhere reliable. Preferably a DNS service because you also get DNS management this way. My recommendation is [DeSEC](https://desec.io/) because it's a German, privacy-oriented non-profit and it has a modern interface and modern features like an API, security tokens, support for recent record types, DNSSEC etc. And if you later decide to get a paid domain you can keep using DeSEC for it very easily. Secondly, does your fediverse single-user server really need to be exposed to the internet to get updates? Can't it pull them from other servers? That way you would reduce your risk a lot.
-
@Oha@lemmy.ohaa.xyz 2026-06-11 05:43
point the AAAA/A records to your corresponding ips and allow incoming traffic on port 443, 80 on your Firewall. You may also need to set up a dyndns client if your isp changes your ipv4 frequently.
-
@potatoguy@mbin.potato-guy.space 2026-06-11 03:17
In your scenario, I would prefer to tunnel to the outside, as it could be risky to just open a port on your router and open a port on your computer. In this case, pointing the IP to a vps that your PC tunnels to or putting the record in cloudflares DNS, that way no automatic port searcher will try to nuke your network. There is dynamic DNS too. There is cloudflare and other [options](https://github.com/anderspitman/awesome-tunneling) too. Edit: I do this with cloudflare, but privacy is very much not given with them.
-
@A_norny_mousse@piefed.zip 2026-06-11 04:18
Do you have a static IP? Just point your domain to that. I only have A- MX- and CNAME-record. A is for the numerical IP. MX is for mail, I don't use it. CNAME is for subdomains afaics (currently only contains www). All fields are comma-separated lists. NS stuff is for if you're running a nameserver and I never even looked into it.
-
@adarza@piefed.ca 2026-06-14 08:49
from what i know about 'gname' is that they're popular with scammers and other bad actors. i would steer clear of them, even if they are 'free'.
-
@Decronym@lemmy.decronym.xyz 2026-06-14 08:50
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread: Fewer Letters | More Letters ---|--- DNS | Domain Name Service/System TLS | Transport Layer Security, supersedes SSL VPS | Virtual Private Server (opposed to shared hosting) ---------------- [Thread #11 for this comm, first seen 14th Jun 2026, 08:50] [[FAQ](http://decronym.xyz/)] [[Full list](http://decronym.xyz/acronyms/selfhosted@lemmy_world)] [[Contact](https://hachyderm.io/@Two9A)] [[Source code](https://gist.github.com/Two9A/1d976f9b7441694162c8)]