What's the easiest way to set up a domain on a local network?

Question

Computer networks

Googled a lot, but there are all some abstruse discussions. The task is simple: I have WAMP, I have a website on a machine, I want to enter on a mobile device connected to the vasyapupkin local network and get to the site. Without proxies, hosts and other unnecessary movements. I imagine this: in the wi-fi router, I specify the ip of the machine running WAMP as DNS. There is also some kind of DNS server running on the machine, which resolves the url to 127.0.01, through which apache then redirects to the site (by the way, is it possible to resolve the url to 127.0.0.1/something?) There are no kettles on Google.
Tell me what to do. Especially what to allow windows firewall.
By the way access directly on IP by means of the Apache already adjusted.

Answer 1

(By the way, can the url be resolved to 127.0.0.1/something?)

No. If it's simple, then the DNS translate IP into names and vice versa. It doesn't resolve the URL.
The easiest way is if your router can play DNS server. Of the cheap ones, these are Mikrotiks and others with VRT firmware.
And this is already more complicated than the first method, since you need to install and configure the DNS server on your computer, which should always be on, if you have WAMP on the same computer, then there will be no problems with this.

Answer 2

DNS has nothing to do with urls. DNS is a global distributed base in which keys and data are registered :) Usually the key is IP, the given is the name (or other data - mx, for example), but there are also reverse bases, where the key is the name.
By the way, hosts is a very simplified version of DNS, so without "simple movements" it will not work. The scheme is quite normal, but you just need to specify not 127.0.0.1, because 127.0.0.1 is "myself", but the IP that the computer with WAMP has

Answer 3

server OS? If yes - through the management of the server, stick the DNS role. Then, in the DNS management snap-in that appears, create a new Primary Forward Lookup Zone, with name = your site name (not url - only DNS name). for https://toster.ru/q/54575711- this is toster.ru. In the DNS properties of the server, specify as DNS Forwarders the DNS you need, to which to forward all other DNS requests of the client, for example 8.8. In this zone, create an a-record without a name, indicating the ip of your server hosting the site (the ip address must be accessible from the local network). On DHCP, distribute the address of your DNS server as a DNS. Thus, you will ensure that when you try to go by the name of the site, you will be given the ip of your server.
Further, if you have not customized the ports, then allow port 80 for http and 443 https on the firewall, and it should be yours now.) You will give URLs and other stuff from the web side.