View Single Post
  #8   Spotlight this post!  
Unread 02-12-2013, 13:50
techhelpbb's Avatar
techhelpbb techhelpbb is offline
Registered User
FRC #0011 (MORT - Team 11)
Team Role: Mentor
 
Join Date: Nov 2010
Rookie Year: 1997
Location: New Jersey
Posts: 1,624
techhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond repute
Re: ping and tracert networking question

Quote:
Originally Posted by stevep001 View Post
I'm with others who are hypothesizing that you're having link level problems. DNS issues in ISPs get fixed very quickly, as working DNS is required for nearly everything else that ordinary people do on an internet connection.
Ether might be having packet loss issues that are tending to impact the small DNS transactions and so when he repoints his DNS to another source that has their DNS parameters set differently it might be more reliable.

So it could be both.

A good way to notice would be to run a ping or performance test against a relatively stable local site and see if there are periods where it takes much longer to respond. It's probable something in the link is retrying to make the delivery in that case.

I have used *a lot* of Hughes Networking satellite gear and DNS transactions were a major pain because the small transactions would easily waste a ton of time clearing the satellite uplink and back (2-4 seconds of lag to complete a DNS request over bi-directional satellite is not unusual). This sort of thing can make a big headache if the pages you most frequently visit contain absolute encoded hyperlinks with the domain listed. Sometimes the DNS will keep being looked up and avoid the requester cache...especially if they've set the time to live low. Also the DNS packets are usually small and usually satellite TCP/IP systems send a big block to give the illusion of broadband...till you only need a tiny DNS request...then the rest of the block is wasted because your need to resolve the DNS first. It was often annoying enough I'd setup a local caching DNS server and use a 56k modem to feed it (which sounds painfully slow till you realize that the modem's latency is magnitudes less).

It's true that Ether's radio connection should have much lower latency. However the path between the radios in the link is probably open to interference of many kinds. Any of them might be occasionally impacting the link performance causing headaches. I've set up hundreds of long distance wireless links and it is not an uncommon issue.

Ether is there any chance the service provider will let you use SNMP to their radio to get the statistics?
The advantage to them is that they don't need to give you the administration password for the web / command interface.

Last edited by techhelpbb : 02-12-2013 at 14:03.