Do I need a second domain to run my own authoritative dns server? (lemmy.world)

submitted 7 months ago* (last edited 7 months ago) by raldone01@lemmy.world to c/selfhosted@lemmy.world

16 comments fedilink hide all child comments

I have a static ip (lets say 142.251.208.110).

I own the domain: website.tld

My registrar is godaddy.

If I want to change my nameserver godaddy won't allow me to enter a static ip. It wants a hostname. I observed that many use ns1.website.tld and ns2.website.tld.

I don't understand how this can work because ns1.website.tld would be served by my dns server which is not yet known by others.

Do I need a second domain like domains.tld where I use the registrars dns server for serving ns1.domains.tld which I can then use as the nameserver for website.tld?

I would like to avoid the registrars nameserver and avoid getting a second domain just for dns.

Thank you for your input.

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

[-] hayalci@fstab.sh 7 points 7 months ago

I use porkbun.com for my domains, which is excellent, and also has glue record support.

https://kb.porkbun.com/article/112-how-to-host-your-own-nameservers-with-glue-records

[-] raldone01@lemmy.world 2 points 7 months ago

I just switched to porkbun. Saves me about 20EUR per year. Thanks for the tip.

I missed the keyword "glue records". Ultimately I managed to get my dns server to work but decided against using it for now as the acme plugin is not able to do what I want. https://github.com/mariuskimmina/coredns-tlsplus/issues/2

[-] hayalci@fstab.sh 2 points 7 months ago

Yeah porkbun is good.

To see how the glue records work, you can run dig +trace example.com

This answer goes into detail how it works behind the scenes.

https://superuser.com/questions/715632/how-does-dig-trace-actually-work

this post was submitted on 10 Apr 2024

13 points (88.2% liked)

Selfhosted

40198 readers

427 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz