DNS Issues SLOW

  • 1
  • Question
  • Updated 3 weeks ago
  • Acknowledged
Quick question,

Is anyone else noticing slowdown on the DNS servers? Might just be the beam I am on. Not sure just curious if anything is going on. How can I tell the DNS server and ground station for my area. I am in northwest Florida. 
Photo of michael3245

michael3245

  • 39 Posts
  • 6 Reply Likes

Posted 3 weeks ago

  • 1
Photo of VeteranSatUser

VeteranSatUser, Champion

  • 2768 Posts
  • 1523 Reply Likes
Run a Tracert and see what you are seeing through that.
Photo of michael3245

michael3245

  • 39 Posts
  • 6 Reply Likes
To any location or IP address?
Photo of michael3245

michael3245

  • 39 Posts
  • 6 Reply Likes
a quck trace route to anything. Looks like on the 6th hop it is coming out of Seattle wa
Photo of VeteranSatUser

VeteranSatUser, Champion

  • 2768 Posts
  • 1523 Reply Likes
To like www.google.com.

I believe your gateway is Juneau Alaska.
Photo of michael3245

michael3245

  • 39 Posts
  • 6 Reply Likes
Hope this helps some sorry edited out my local ip address for my security router and exede modems. 


Tracing route to google.com [172.217.3.206]
over a maximum of 30 hops:

  
  3   611 ms   598 ms   612 ms  10.75.12.220
  4   610 ms   644 ms   635 ms  10.75.10.30
  5   644 ms   639 ms   636 ms  10.95.240.161
  6   641 ms   641 ms   628 ms  six.sea01.google.com [206.81.80.17]
  7   633 ms   641 ms   714 ms  108.170.245.113
  8   711 ms   637 ms   627 ms  108.170.233.155
  9   642 ms   637 ms   665 ms  sea15s12-in-f14.1e100.net [172.217.3.206]

Trace complete.

C:\Users\Micha>
(Edited)
Photo of M.E.M.

M.E.M.

  • 64 Posts
  • 34 Reply Likes
My DNS quit completely several days ago. I am on beam 328. I could not even address my router or Viasat modem when connected by ethernet. The same with web pages. 

I called Viasat customer service and they scheduled a tech appointment for me in two weeks.

I decided not to wait and to try different things at random.
Finally, I uninstalled my Realtek network adapter in Device Manager, deleted my home network, and restored my Windows 7 to a week earlier.

I then reinstalled my network adapter (Windows 7 does this automatically) and reinstalled my home network.

This solved the problem and everything is back to normal.

So I contacted the Viasat tech company and left a voicemail that he did not need to come. I don't think the tech could have solved this problem if he had come.

What to you think, Andy Schack? What do think the tech would have tried if he had come here, given that the problem had nothing to do with Viasat equipment, Are the typical techs qualified to diagnose Windows software problems?
Photo of Judge and Jury

Judge and Jury

  • 1607 Posts
  • 931 Reply Likes
 
When that problem arises, look at the adapter's IPv4 properties for the DNS server.  This can disappear sometimes.  I use static addresses here but the DNS and IP addresses can be set to automatic.  Using static numbers lets you see instantly how your connection is really configured.  The DNS should be set to your gateway address since ViaSat is going to commandeer the DNS anyway.  This makes your router deal with DNS, not your computer (no internal arguments and resorting to fallback DNS).  If the DNS address disappears in you adapter properties, everything seems  to be fine, like it should work, but not even the router is accessible.

This pic is from Windows 7...



Photo of VeteranSatUser

VeteranSatUser, Champion

  • 2768 Posts
  • 1523 Reply Likes
I hop through Seattle at one point too, as I go through the Winnepeg gateway.  I haven't noticed any issues with my DNS.  So yes, it could be a local related issue as described above.