I can't find a problem with DNS on Windows Server 2019 when redirecting a name to a local address. What are the pitfalls?

Question

Domain Name System

Our organization has a Windows Server 2019 virtual server with AD+DNS (IP 10.0.0.4) and a WEB server with a website where our users work (IP 10.0.0.16). We have a WAN speed of 25 MB / s and the task was set for domain users to directly connect to the server via a URL link.

Seems like a simple task. Here are my steps:
1) on the DNS server I add a new forward lookup zone -> For all DNS servers running on the domain controller -> in the "Zone name" I write the URL -> I disable dynamic updates
2) In the new zone I add a new node A and I prescribe only the IP address of the WEB server (then the name will have the address 10.0.0.16).

After that, for the most part, the site does not work, "ERR_CONNECTION_TIMED_OUT" (the NSLOOKUP and PING commands refer to the correct address by name). Reset cookies, run from other browsers. The site works \ does not work regardless of whether the PC is in the domain or not. Of course, all PCs have the address of our DNS in the first line.

If anything, the address AAA.BBB.ru and when loading the page immediately throws it at AAA.BBB.ru/Login.

According to the same scheme, I put it on other names and worked quite successfully

Answer 1

Show a tracer to the name in problematic moments.

Answer 2

Check the firewall settings on the web server side, most likely you have closed incoming connections on 80/tcp or 443/tcp.