DNS remains for Domain Name Server and is a server in charge of making an interpretation of site space names to relating IP addresses of servers which have these areas. So for instance when you write www.microsoft.com your program doesn’t know which server it needs to contact to recover pages for www.microsoft.com area. To get the address of the facilitating server program first tries to contact close-by DNS server and get facilitating server IP address there. In the event that nearby DNS server is not able to discover this data it will reroute the solicitation to another DNS server which has more address interpretations on it. When address is determined it will be returned back to your program and it can begin building up connection to destination site.
In the event that something separates in your local DNS server or on the off chance that it not able to contact next DNS server in line then the space name you write in your program won’t get interpreted into IP address and your program will neglect to build up the connection. This blunder is typically not obvious to the web client since program will simply continue attempting to stack the page until it can resolve DNS. So everything except for DNS server could be working fine yet web still will be unusable.
There is an awesome approach to minimize impact such issues can have on you. Rather than using DNS servers given by local web suppliers you can utilize Google or
OpenDNS DNS servers.
Google DNS IP addresses:
8.8.8.8
8.8.4.4
OpenDNS IP addresses:
208.67.222.222
208.67.220.220
You can indicate these IP addresses as your default DNS servers and each time your program should make an interpretation of space name to IP address it will go straightforwardly to these servers rather than nearby DNS server. Since these servers are facilitated by Google and OpenDNS in an exceptionally dependable manner the shot of them not living up to expectations is much lower than that of local DNS.