On Thu, 2007-08-09 at 04:30 -0500, Linus Ulrick wrote: > Hello, Everyone > I hope that one of the many geniuses that frequent this list might be > able to shed some light on a problem that I am having. I do run Fedora > Core 6 (very happily, I must say :)) but this is too off topic, please > feel free to contact me off list. > > I have fully qualified domain: afolkey2.net. It can USUALLY be found > thusly: > http://www.afolkey2.net > > Tonight when I came home from work, I started seeing problems with > pages loading. Try the following to see what I mean: > http://www.afolkey2.net/awstats/awstats.pl?config=www.afolkey2.net > http://www.afolkey2.net/gallery2/main.php > > I use the free dynamic dns service from dnsexit.com. The nameservers > that they have me point my domain to are as follows: > ns1.dnsexit.com > ns2.dnsexit.com > > When I noticed the severe issues described above, I ran "ping" on each > of those two servers. The edited results of "ping ns1.dnsexit.com" > look something like this: > PING ns1.dnsexit.com (63.223.76.173) 56(84) bytes of data. > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=1 ttl=48 time=417 ms > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=2 ttl=48 time=436 ms > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=3 ttl=48 time=375 ms > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=4 ttl=48 time=349 ms > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=5 ttl=48 time=258 ms > > --- ns1.dnsexit.com ping statistics --- > 49 packets transmitted, 46 received, 6% packet loss, time 48033ms > rtt min/avg/max/mdev = 91.901/433.380/827.993/223.834 ms > > That didn't look very fair :), so I ran ping on that server again: > PING ns1.dnsexit.com (63.223.76.173) 56(84) bytes of data. > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=1 ttl=48 time=88.1 ms > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=2 ttl=48 time=98.5 ms > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=3 ttl=48 time=89.0 ms > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=4 ttl=48 time=86.9 ms > 64 bytes from ns1.dnsexit.com (63.223.76.173): icmp_seq=5 ttl=48 time=89.0 ms > > --- ns1.dnsexit.com ping statistics --- > 87 packets transmitted, 84 received, 3% packet loss, time 86027ms > rtt min/avg/max/mdev = 85.584/91.493/108.933/4.825 ms > > But, if I run "ping ns2.dnsexit.com" the results (again edited) look > like this: > > PING ns2.dnsexit.com (64.182.102.188) 56(84) bytes of data. > 64 bytes from nd188.dnsexit.com (64.182.102.188): icmp_seq=1 ttl=53 time=23.2 ms > 64 bytes from nd188.dnsexit.com (64.182.102.188): icmp_seq=2 ttl=53 time=23.1 ms > 64 bytes from nd188.dnsexit.com (64.182.102.188): icmp_seq=3 ttl=53 time=21.1 ms > 64 bytes from nd188.dnsexit.com (64.182.102.188): icmp_seq=4 ttl=53 time=18.6 ms > 64 bytes from nd188.dnsexit.com (64.182.102.188): icmp_seq=5 ttl=53 time=23.3 ms > > --- ns2.dnsexit.com ping statistics --- > 42 packets transmitted, 42 received, 0% packet loss, time 41040ms > rtt min/avg/max/mdev = 18.630/25.121/40.702/4.839 ms > > > > In this case, the times seem much quicker, and you will notice that > unlike when I pinged ns1.dnsexit.com, there was no packet loss. Check the list of packets and see if you have out of sequence or missing sequence numbers. If all that's missing are the last few (most likely with delays >25mS), what you're seeing is that hitting CTRL-C aborts the program before those last few packets are received. > But > you will also notice that when I ran "ping ns2.dnsexit.com" that the > server that appeared to be the one that was queried is > "nd188.dnsexit.com", not "ns2.dnsexit.com" That's an alias (CNAME). No big deal. > I don't know what (if any) the significance of that fact is. I merely > observe it. > > If nothing else, I THINK I can safely assume that they are having some > issues on their end. Nonetheless, do any of you have any suggestions > about free dynamic DNS services that you have had good fortune with? > > Anyway, thank you in advance for any help that you may be able to give > me. Run several traceroutes to the DNS servers and the website in question. You may find an overlength route or possibly discover a flapping route with one of the ISPs. This is information their support groups will want to have. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens@xxxxxxxxxxxx - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Beware of programmers who carry screwdrivers - ----------------------------------------------------------------------
