Problems and misunderstandings when registering a domain, how to publish a site?

Question

JavaScript

Hello! Another problem and / or misunderstanding. Forgive me not to scold strictly, I'm trying to delve into it)
Raised the Windows Server 2016 server. AD, DNS, IIS + PHP, MySQL. According to the circumstances, all this is on one server, but according to the words, AD will soon be on another server. I set up AD, created the aemtk.edu.kz domain, users and rights, set up the GP, raised the DNS, everything works fine. Then I raised the IIS server with PHP binding. Created a website, set up a redirect on the router, everything works fine. the site is accessible by IP address on the external side. The site is also available locally via the aemtk.edu.kz domain.
Now I want to buy a domain. aemtk.edu.kz from the registrant. Registered on their site, Step 1. create contacts. Administrator, technical, financier, created everything. Step 2. Asks to create a host, that is, an NS server. Here there was a problem. what should I put in there? entered ns.dc1.aemtk.edu.kz into the server name. in the IP field entered the external IP: 180.0.130.248. constantly getting rejected. changed the server name to ns.aemtk.kz and left the IP the same. The request was approved but assigned a different ip: 88.204.198.235. whois on this ip gives out a completely different city and a different provider. I called my provider, explained everything to him, said that I now have a DNS server up. He said okay, now we'll add a PTR record. he requested the DNS configuration. The provider at itself registered record. nslookup gives the following information:

nslookup
╤хЁтхЁ яю єьюыўрэш■:  DC1.aemtk.edu.kz
Address:  192.168.1.2

> set type=PTR
> 180.0.130.248
╤хЁтхЁ:  DC1.aemtk.edu.kz
Address:  192.168.1.2

Не заслуживающий доверия ответ:
248.130.0.180.in-addr.arpa      name = DC1.aemtk.edu.kz

I want to ask connoisseurs and experienced comrades:
1. Is it okay that the name of the PTR host is "DC1.aemtk.edu.kz", when the site should be called aemtk.edu.kz? that is, the provider has registered so at home
2. in the DNS parameters "NS Name Server" => dc1.aemtk.edu.kz => 192.168.1.2 is this correct? Or should there also be just aemtk.edu.kz?
3. What to specify in the request to the domain registrant in hosts, Name: ns.dc1.aemtk.edu.kz, IP: 180.0.130.248? would that be right? and as an alternative NS server, specify the DNS address of the provider?
4. To publish a site so that it is accessible by domain, what else should be registered in your DNS server?
External IP static: 180.0.130.248
Server address: 192.168.1.2
Server name: DC1
DNS name: dc1.aemtk.edu.kz
NS record: dc1.aemtk.edu.kz
Thank you all!)

Answer 1

created() { //при создании
  Service.getIP().then(response => {
    console.log(response);
    this.$store.dispatch('setIP', response); //идем к action в стороннем файле
  })
}

or so

async created() { //при создании
  const ip = await Service.getIP();
  this.$store.dispatch('setIP', ip); //идем к action в стороннем файле
}

Answer 2

For the future - structure the text. I read about a third, I kind of understood the meaning of the problem, the rest is just too lazy to read ...
1. You are confused by the terminology. "Domain" in AD and "domain" in tyrnet are not the same thing at all.
2. NEVER host sites on an AD server! Virtualization is everything. If you want to have some fun with Billy's virtualization, install Hyper-V, it's fine for Windows. The AD server should be ONLY AD. Well, there may still be other system snap-ins - internal DNS, DHCP, certificate service, WSUS ...
3. If there is no experience in Linux, it is better to put the site on hosting. Honestly. IIS is better right away, like a bad dream...
4. If there is no understanding of how DNS works, then it is also best to buy DNS from Provo, usually large providers offer it. And NEVER keep on Windows services that are directly accessed from the outside, no matter how harmless they may seem!
5. If you don't want to donate to hosting - raise a virtual machine with linux, on which you will start both the site and DNS.

Answer 3

The easiest and most correct way to solve the problem in your case is to use the DNS hosting service and not to fuss with creating your own name server for the domain name, which should be available on the Internet (and in general, the practice of placing everything on one server is extremely negative, especially when it comes to DNS service). Use, for example, free Yandex.DNS (pdd.yandex.ru) or paid Zilore DNS (www.zilore.com). Add your domain there, create the necessary records pointing to your external server IP (A record for addresses, MX for mail), and at the domain name registrar, register the DNS server of the DNS hosting provider that they will provide you for your added domain name.

Answer 4

This is a variant of shooting in the leg with an anti-tank grenade launcher ...
Before it's too late - change the AD domain name to any "non-internet" one, for example aemtk.edu. local