Rookie consult web server higher-ups, now I have 2 servers, LAN address is 10.2.12.88/10.2.12.86 respectively, the problem domain to gw.test.com,
Network as shown in figure: DNS to external IP (120.205.22.33, literally write an external IP), mapping to the Intranet server 10.2.12.88, Intranet server 10.2.12.88 DNS, were the new host to multiple secondary domain name, the multiple secondary domain name on the server can be normal external access, but there is a secondary domain name to 10.2.12.86 namely gw.test.com inaccessible,
Trying to solve the methods and results: (1) the external IP address 10.2.12.86 map directly to a network server, accessed through gw.test.com can normal 2. LAN internal DNS 10.2.12.88 instead of computer, networking is constant, the server 10.2.12.86 can access through gw.test.com,
Other note: gw.test.com is win2008 10.2.12.86 64 server, the deployment of software is wampserver3.0.6 _x64_apache2. 4.23 _mysql5. 7.14 _php5. 6.25-7.0.10
Rookie consult web server higher-ups, need how to set up, through the domain name gw.test.com to make any computer can access 10.2.12.86 resources, thank you?

CodePudding user response:

Through the DMZ mapping should can be achieved, specific baidu

CodePudding user response:

Describe a bit messy... I direct way to deploy, you look at compare
10.2.12.88 DNS server
10.2.12.86 WEB server
120.205.22.33 IP networks outside

Your hands are a domain name, the domain name registrar. (if you did not transfer) will give you a background, give you add, need to release 10.2.12.86 sites on this server:
1. The domain name registration business management background, add A new record gw.test.com - & gt; 120.205.22.33
2. In the LAN 10.2.12.86 gateway device, do the mapping, can be 120.205.22.33 - & gt; 10.2.12.86 IP mapping, also can be 120.205.22.33:80 - & gt; 10.2.12.86:80 (a) suggest behind the port mapping, if there is a firewall, also want to add a "allow" access to the web service strategy
In this way, outside the network can access the site you
(if at home, domain name must be put on record)

Do network part, now finish can make network users access to the web site:
1. On 10.2.12.88, DNS service installed, add the test.com domain, A new record gw.test.com - & gt; 10.2.12.86
2. On 10.2.12.88 DNS forwarding, forwarding servers fill your ISP DNS
(3) sets the Intranet user DNS server to 10.2.12.88
(1 in operation, do not resolve to your IP networks outside, in most cases, this setting will meet with NAT loop problem, the result is directly to the target inaccessible, simple understanding is NAT cases can't access the router again when the local area network resources)

If your router support custom DNS, can be directly on your router network part of the operation, it saves a DNS server:
1. Add custom DNS entry gw.test.com - & gt; 10.2.12.86
(2) sets the Intranet user DNS servers to gateway IP

CodePudding user response:

. Your 88 is not a DNS server? Then you change the internal DNS server to do 88?