To get around this problem, DNS information is shared among many servers. But information for sites visited recently is also cached locally on client computers. Chances are that you use google.com several times a day. Instead of your computer querying the DNS name server for the IP address of google.com every time, that information is saved on your computer so it doesn’t have to access a DNS server to resolve the name with its IP address. Additional caching can occur on the routers used to connect clients to the internet, as well as on the servers of the user’s Internet Service Provider (ISP). With so much caching going on, the number of queries that actually make it to DNS name servers is a lot lower than it would seem. See the link for a similar error “Unable to register a client to Domain“.
The Domain Name System (DNS) is one of the foundations of the internet, yet most people outside of networking probably don’t realize they use it every day to do their jobs, check their email, or waste time on their smartphones. At its most basic, DNS is a directory of names that match with numbers. The numbers, in this case, are IP addresses, which computers use to communicate with each other.
In my case, as shown below, The IP parameters were correct. I resolved this issue by flushing the DNS cache. Below are the steps to perform this.
– Open command prompt on Windows and
– run the following commands below.
The commands are vital in releases and renewing your IPs. In the future, I will more on these commands
ipconfig /flushdns ipconfig /release ipconfig /registerdns ipconfig /renew
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.