The domain and site name are the same. How to set up DNS?

Question

Domain Name System

I know that the problem is illiterate and has long been studied. But the second day I struggle I can not fix it. As usual, there is a local domain.ru domain and a site on the Internet with the same domain.ru name.
The internal network is served by a Windows 2008R2 DNS server.
Employees of the local network cannot access the site www.domain.ru, as they are redirected to the domain controller.
What I tried:
1) Added a www A-record with the IP address of the site. Here is another problem. The provider has many sites on this IP address. Accordingly, the site does not open by direct ip . After adding the A-record, nothing changes. All the same, requests go to the domain controller.
2) I tried to delegate the www record using the built-in DNS tools, indicating the provider's ns-servers. This option didn't work at all. The site does not open, nslookup did not show the site address.
3) I tried to install IIS on the domain controller and redirect to www.domain.ru, but after that, when the site is opened, all browsers endlessly redirect like crazy to domain.ru, that is, to an empty place.
ipconfig /dnsflush before each check did.
It was possible to achieve the work of the site only if you add one more entry A
(as a top-level folder) - A - 89.111.177.122
(as a top-level folder) - A - 192.168.0.1
(as a top-level folder) - A - 192.168.0.2
www - A - 89.111.177.122
Than it can threaten in operation of the domain? Now while internal addresses resolve correctly and there are accesses where it is necessary. Is it possible to leave it like that? After all, as far as I understand, browsing goes in order, which means that if it sees a directory at 192.168.0.1, it will not look further and will never reach the external address.

Answer 1

Yes, it turned out that redirection from www to non-www was set in the code of the site page for reasons of site promotion. Therefore, all tricks with local DNS will not help.
We will make a mirror of the site in the local network.

Answer 2

works? Do not touch!

Answer 3

All solutions with DNS are half-hearted. Deploying a full-fledged site mirror on a DC is a controversial decision.
I tried it myself and I advise: deploy IIS on domain controllers, create the domain.ru site there, configure redirection to www.domain.ru on it. If your site uses SSL, install a certificate for the domain.ru and www.domain.ru addresses on the domain controller and specify it in the bindings.