I decided to kill the site on my home server. I connected the service with the service provider "Static IP address", my domain is delegated on Yandex, and on Yandex in the DNS settings I wrote: Host = @, type = A, record value = 46.x.xxx.196 (my IP). On the router, respectively, forwarding port 80 to the server. While the DNS was being updated, I created a level 3 domain in blog.% My_domain% .com in apache2 and rolled in a fresh WordPress. Something passed about 6 hours, the main domain became available, the domain of the 3rd level is not. I called a friend, he says, they say, you make another A-record, just put a star in the "Host" field instead of a dog. I added another entry, it turned out like this:
At the moment, more than a day has passed, the main domain of the 2nd level is accessible from everywhere normally, and the domain of the 3rd level from the phone (Yota 4G) loads perfectly, and from my computer (connected to the same router as the server) it loads sooooo slowly, and As a result, in 90% of cases, it falls into "Page not found." I don’t know where my mistake is and what it’s wrong for me, but I generally need ALL *.% My_domain% .com requests to go to my IP, and then I’ve been using apache to regulate what to process and how.
There was a thought that I missed something else besides DNS, since From the company, the site starts to load, the title is loaded, the background image is loaded, and then everything just drops, that is, maybe this is not the case in the DNS, but then what?
PS In the course of testing by throwing links to friends, it turned out that the site opens once, someone first writes "Can not get access ... blah blah blah", and immediately after updating the page opens, someone immediately opens , someone does not open at all. Still DNS'y? ..