Cleverly set DNS to speed up wks

A small local area network composed of thirty machines. The Server uses Windows 2000 Server, and the workstation is Windows 2000 and Windows XP. The company uses ADSL Broadband, and the current popular broadband routing method is used for sharing.

In the settings, the workstation is set in this way, that is, the gateway address is set to the IP address of the router, and the DNS is set to the DNS address of the local telecom, I am relieved to see that everyone can access the Internet normally.

However, after a period of time, the problem was discovered, that is, after the user name and password of the workstation are entered during logon, the network logon speed is extremely slow and slow, which is intolerable. If the router is disabled, it is slower. My first thought was a DNS problem, because when Windows 2000 was started, the domain controller was chosen based on DNS. According to this idea, I changed the DNS of the workstation to the IP address of the domain controller, the speed is very fast, but this introduces a new problem, that is, if you change to the domain controller address, you can only open the Intranet homepage but cannot open the Internet homepage, prompting you that you cannot open the search page, in fact, it cannot be parsed.

After my exploration, I found that this method can be used to solve this problem: IP Forwarding is performed on the DNS server. The principle is that if the DNS server cannot resolve the domain name at present, it forwards the request to a higher-level DNS server for resolution. The operation is to open the DNS console, right-click the DNS server object, click Properties, click the forwarder option, and enter the IP address of the local telecom DNS server in the IP address box, then, click Add (before that, make sure that the gateway of the DNS server is set as the IP address of the router) to completely resolve the conflict between slow startup and Internet access.

Note: There is a problem here, that is, some machines are grayed out. In this case, please go to the DNS console and expand the + number in front of the server, it will be marked with a period (.).

Later, I remember that many people were confused about the problem that you built a website on the Intranet. How can you ensure that the website can be connected to both the Intranet and the Internet? I think using DNS forwarding should solve the problem!