New
#1
Problems with network converting hostname to ip address
For the last several weeks. I've been having a problem with Firefox taking several minutes to find and start loading a sites web page. Firefox tends to hang on looking for hostname. Once the site is loaded it still takes several minutes for the site to fully load. I also found that if I ping google.com from a powershell window it takes several minutes to respond. If you open a bash window and ping google.com it respond almost immediately. Also Microsoft Edge seems to work. It opens the hostname very fast. It seems that if is having problems with dns. I used Microsoft network monitor 3.4 to trace what is happening. From the trace I can see that the dns request gets a response in less that a second. But for some reason the application does not get the response for a long time.
If I reboot the system the problem seems to go away. Yet at some point in time it is back.
Anybody else having this problem?
Windows 10 pro build 10.0.18363 build 18363
- - - Updated - - -
Today I had to reboot the system I thought that it would fix the problem like it has in the past. But after the reboot I still had the problem. I also had a problem starting BeyondTV. It would open the starting window then freeze. No matter what I did I could not get BeyondTV to start. So I tried to boot in safe mode. In safe mode it would start. But It would not show any TV channels. The first safe mode boot was without the network. I then tried to reboot in safe mode with network. Again BeyondTV started but would not show any TV. So I did another revoot in normal mode. This time BeyondTV started and I was able to show TV channels. But a ping of google.com from the powershell window was very slow.
Why is it that Edge can get the google.com web site fast. But powershell can't get an IP address for google.com fast?