How to set up your own DNS to work in the global network?

Question

linux

In the initial data:
1) a local network that goes out into the world via 1 white ip (a standard star with a core computer on Linux as a gateway)
2) a dns server (Linux) in the local network
3) a server with a lamp distributing site
4) possibly other servers for which will also be useful in the future a domain name
Question: as a thought experiment, what should be the sequence of actions if I want to start my own domain (buy? steal? rent? sell my soul to the admin devil?) to an existing white address (for example mneprostointeresno.ru ) , after allowing on your dns, local servers (something like ftp.mneprostointeresno.ru or lamp.mneprostointeresno.ru ) and provide access to them from the global network.
For trut admins, please do not throw stones strongly, I would be extremely grateful if you even throw off links to training materials (if, of course, in the topic)

Answer 1

in order to start using mneprostointeresno.ru, ftp.mneprostointeresno.ru, lamp.mneprostointeresno.ru you do not need to raise your DNS at all. You can use the registrar's DNS and specify several class A records, for example ftp.mneprostointeresno.ru=123.123.123.123. But if you want hardcore (and I think it will be hardcore in your case), then leave an NS record with your IP at the registrar, and your dns server will already inform users of the IP addresses of your lalaly.mneprostointeresno.ru (you will also need to add them, only now at home) Well, open ports 53 for DNS 80 for HTTP and so on for all services that will look outside
UPD: local servers - it's not clear here

Answer 2

The task is divided into at least two.
1. Registration of the domain name mneprostointeresno.ru. This is done by any registrar. To set up ftp, www, ns, etc. names. it is not necessary to raise your DNS - registrars provide Primary-DNS services. This solution has pros and cons. Pluses - nothing to raise, everything is edited in a more or less friendly interface. Cons - in the absence of communication and the need to change something, you will have to break off until the connection appears. Therefore, the best thing to do is:
2. Run your own DNS. The bind is launched, the necessary records are formed (SOA, NS, A, MX, etc.) and the IP of the north with the bind (white, if it is behind NAT) is indicated at the registrar as the primary DNS address. Secondary DNS recommend to take directly from the registrar - it's easier to set up.
Articles on configuring DNS for a small office. Old ones from 2006, but not much has changed in DNS since then :) Creating and Managing DNS Zones, Part 1 and Creating and Managing DNS Zones, Part 2