~~~
This never happened until I flushed my dns. Is there a step I missed? Or is my computer not used to it?
The DNS cache is kept in RAM. It goes away every time you restart the computer. The only reason why you would want to issue the command to flush it via the command prompt is when you don't want to restart your computer. You did no harm in flushing the cache.
This is easy to test:
Surf to several websites
Open a regular
command prompt window
Type in
ipconfig /displaydns and press enter
That should give you a list of dozens of cached IP addresses.*
Restart the computer and quickly...
Open a regular
command prompt window
Type in
ipconfig /displaydns and press enter
That should give you a list of very few cached IP addresses.*
*If the service named
DNS Client is disabled or not running...
...you should see:
Could not display the DNS Resolver Cache.
Your computer can function just fine without the service named
DNS Client running. Each request to turn a URL or FQDN into an IP address will just have to go to a DNS server or be resolved some other way (e.g. HOST file).
Hi There
I see that you have flush dns.. Who will register it??
Please try ipconfig /registerdns ( make sure use elevated cmd )
Cheers
Registering the client happens with each reboot (if the default settings are present for the network adapter in use). This registration helps other computers connect to the OP's computer name or alias. The OP is having trouble in the other direction.
~~~
It worked, however, ever since then I now have DNS issues usually on boot up. When I would open my browser to google or any other site it displays a DNS error. I have to wait 2 minutes, refresh and then I'm able to surf the internet. The same applies for my skype. I'm unable to call, however, I can still send IMs. This happens every time I start up my PC and occasionally here and there.
~~~
I wonder if Skype caches IMs until they can be sent.
The "occasionally here and there" part is interesting. When this happens to you, can coworkers still surf?
DNS problems should not impact traffic that already knows the IP address of the remote computer... so pinging Google by one of its IP addresses should work (if pings are allowed thru the company firewall). See
this post. You could leave that ping running and when you have trouble "occasionally here and there", un-minimize that command prompt window and see if the pings are still happening. [If pinging Google is not allowed, then pick an IP address inside the company firewall.]
As far as not being able to browse to Google right after booting the computer:
Open a regular
command prompt window
Type in
ipconfig and press enter
Take note of the IP address currently assigned to your computer
Ask a coworker to ping that IP address**
(using the "-t" option to keep the pings going until manually stopped)
Turn your computer off
Turn your computer on
(Not just a restart. Cycle the power.)
**this assumes that the two of you are connected to a network that allows for pings and that your computer is setup to respond to them.
The coworker should see the timeouts stop and should start getting good returns long before you can log on to your computer. Of course, this all rests on the hope that your computer will be assigned the same IP address that it had before the power was cycled.
As soon as the computer boots, quickly check the IP address again and quickly start that batch file that pings one of Google's IP addresses. If the computer was assigned a different IP address, then we just wasted some time :-(
If the computer does not have have an IP address assigned yet, then there might be a problem with your DHCP service.
If you are able to ping Google right away, but not browse to Google via a URL, then DNS is indeed the problem. We can chase that problem down once we are sure you are getting an IP within a reasonable time frame after starting the computer.
