Well, I've found that one of the most common problems in enterprise environments is misconfigured DNS addresses on the clients and the servers themselves, which is reflected in the poor performance of the network and access problems certain services such as web pages.
dare
Here is a description of how the right settings with DNS infrastructure, I hope will be useful for all:
-
is very important to have one or more DNS servers the internal network to access computers so friendly, safe, fast and efficient network. Likewise, this server will allow more quickly resolve external addresses to the intranet, through which the service will cache storing the most frequently asked to make all network clients. -
That server must have a static IP address assigned, and this direction should be excluded from the scope of the DHCP server (in which case there is one). -
primary DNS address of this machine should be the server itself. -
When a company buys a service, Internet provider (ISP) provides the addresses of their DNS servers, these addresses will never be set to customers, as they may cause problems and slow speed access services, such as the login process on the network. -
The client machines must configured with the address of the internal DNS servers. -
In the DNS server console in the server properties, on the Forwarders tab, you should add the address provided by the provider (ISP). A forwarder is used only in cases in which a query can not be handled by the local server (because the server is not authoritative for the zone, or because it has in the local cache to externally imposed solution). In this case the server becomes a client and makes the query alos external servers, and to get the answer stored in the local cache in order to resolve more quickly when a customer returns to do the same query.
0 comments:
Post a Comment