Selfhosted

61361 readers

643 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Finding a new registrar/name server for .at (discuss.tchncs.de)

submitted 7 months ago by fatcat@discuss.tchncs.de to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

Hi!

Maybe someone can help me with a problem I’m having, vaguely related to self hosting.

I want to use a domain with let’s encrypt certificates locally. I realise the only way to do this is a (automated) DNS-01 challenge if I don’t want to expose anything to the outside.

Those DNS challenges require my name server to have some kind of API to automate the process. My registrar/name server doesn’t have a API unfortunately.

I want to use the opportunity to switch my registrar and name server in one go, but I’m pretty picky…

My wish list is:

MFA for general account administration
scoped tokens or account for API access (don’t need or want to manage everything by API)
can handle .at domains
not cloudflare
registrar and name server should be one entity if possible
european if possible
supported by ngnix proxy manager if possible

Backup plan would be picking a registrar which supports DNSSEC for .at domains and use desec.io I guess.

But maybe the hive mind has a good recommendation for me? :)

Thank you in advance for reading! I’m aware I’m just a bit extra, but i want to be able to just ignore the whole name server and domain topic for the next ten years again if I can.

Cheers!

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

[–] ikidd@lemmy.world 0 points 7 months ago

Create a cloud flare accounts and change the name servers at you current registrars to what cloudflare gives you when you try to migrate. Its best practice to split up registrar and DNS anyway. then create an API token so your reverse proxy can build records and certbot a new cert.