Cleverly modify the DNS settings to improve the workstation boot speed

The author's environment is a small local area network consisting of 30 machines, the server uses Windows 2000 Server, the workstation is Windows 2000 and Windows XP. The company uses ADSL broadband, and the current popular broadband routing method selected in the sharing mode.

In the setup, the workstation is set up such that the gateway address is set to the IP address of the router, and the DNS setting is the DNS address of the local telecommunications. After this setting, the author can see that everyone can access the Internet normally. It was relieved.

But after using it for a while, I found the problem, that is, after the workstation enters the user name and password when logging in, the login network speed is slow, slow and unbearable, and if the router is turned off, it is slower. . The author's first feeling is the DNS problem, because Windows 2000 chooses the domain controller when it starts. It is based on DNS. According to this idea, the author will change the DNS of the workstation to the IP address of the domain controller. The speed is very fast. But this brings a new problem, that is, if you change the address of the domain controller, you can only open the home page of the intranet and cannot open the home page of the external network, prompting that the search page cannot be opened, in fact, it cannot be resolved. After the author's exploration, I found that this problem can be solved in this way: IP forwarding on the DNS server, the principle is that if the DNS server cannot resolve the domain name, it will forward it to the higher layer. DNS server, requesting it to parse. To do this, open the DNS console, right click on the DNS server object, then click Properties, click the Forwarder option, enter the IP address of the local telecom DNS server in the IP address box, and then click Add (before securing the DNS server) The gateway is set to the router's IP address), so that the contradiction between slow boot and Internet access can be satisfactorily resolved.

Note: There is a problem here, that is, some people's machine repeater is gray. Please enter the DNS management console first, then expand the + sign in front of the server, which will be marked with a period ( .) The area can be deleted.

Later, the author remembers that many people have been confused about one problem before, that is, you have established a website on the intranet. How can you guarantee that you can both access the intranet and the external network? I think using DNS forwarding also It should be able to solve the problem!