How will dns work in this case?

Question

Domain Name System

Let's say I have a website: something1234.my_website.com
This website something1234.my_website.com has never been requested by anyone, for example, I created it 1 minute ago.
If someone wants to go to something1234.my_website.com, how would a dns query work?
1) For example, if a user has 8.8.8.8 registered as a dns server, then 8.8.8.8 itself will eventually be forced to access my site my_website.com, right? after all, 8.8.8.8 does not know the ip address of something1234.my_website.com
2) What will change in this scheme if I have a dns server running on my_website.com, which I myself will raise and run?
3) In general, where can I read exactly about this aspect of dns work?

Answer 1

How public and root servers work (checked dig +trace @8.8.8.8 domain.lel): The
request comes to the public server (they are all recursive for most requests, i.e. they do not own domain records and redirect requests to those who have domain levels in reverse order)
The first stage of recursion is - domain owners ., i.e. root domains of the entire domain name system. They have a record of all the servers managing the first level domains, in your example .com
The request goes to the servers owning the zone .com, they answer which server owns the zone The .my_website.com
request comes to this server and it gives its response to the public server which responds to the client
1) Google Public DNS will contact the DNS server hosting the zonemy_website.com
2) After you change the SOA records in the .com zone through the host to your DNS server, requests from public servers will come to it
3) RFC 1034

Answer 2

Conditions:
You create something1234.my_website.com
The user pings something1234.my_website.com for the first time
1. The system looks in the hosts file, does not find it
2. The system looks in its cache, does not find it.
3. The system makes a request to the DNS server (in your case, 8.8.8.8 is specified)
4. The DNS server 8.8.8.8 checks its rules (similar to hosts), does not find it.
5. DNS server 8.8.8.8 checks its cache, does not find it
6. DNS server 8.8.8.8 accesses the root NS, which is responsible for the .com zone, to find out who is the NS server for my_website.com and receives the NS server that is responsible for my_website.com
7. DNS server 8.8.8.8 calls the NS server that is responsible for my_website.com and requests the IP something1234.my_website.com
8. DNS server 8.8.8.8 receives an IP from your something1234.my_website.com and transfers it to your system, simultaneously storing it in its cache for x time (the storage time is indicated in the NS record, but the cache can be separately limited on the DNS server
9. Your the system receives an IP address from
the DNS server 8.8.8.8 and stores it in its cache for the time specified in the NS record, but in principle the local system cache can be configured differently.