Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
You mentioned problems with video streaming. Were those problems just delays in beginning to receive the stream, or were there actually problems receiving the stream during playback? Problems during playback would not be related to DNS. If DNS response time is really your problem, the simplest solution would be to run your own internal DNS server. DNS is a very basic part of the Internet plumbing, and using a DNS server that's not on your local network will add latency to pretty much everything you do on the 'net. On Dec 22, 2007 8:08 AM, James Kramer <[hidden email]> wrote: > I'll try some of the suggestions and get back to you. > > I was thinking that It may be the DNS server. I am using the DNS on the > router as set up by Verizon. It there a way to check the DNS speed? Can > someone recommend a fast public DNS server? I guess that I could set up a > DNS server on my Linnode server. > > The connection is always noticeably slower on Sunday. I will need to study > wireshark. I remember the discussion here recently. Is there an easy > command? > > Here are the results from traceroute. Traceroute took about 6 seconds to > complete the analysis with a lengthy pause between each route reported but > traceroute indicates 25 ms > > traceroute google.com > traceroute to google.com (64.233.167.99), 30 hops max, 40 byte packets > 1 192.168.1.1 (192.168.1.1) 0.613 ms 1.036 ms 1.155 ms > 2 L100.VFTTP-59.BSTNMA.verizon-gni.net (71.174.56.1) 9.740 ms 11.032 ms > 11.134 ms > 3 P3-1.LCR-06.BSTNMA.verizon-gni.net (130.81.49.230) 13.948 ms 14.087ms > 14.125 ms > 4 130.81.29.174 (130.81.29.174) 14.174 ms 15.943 ms 16.014 ms > 5 0.so-5-1-0.XL2.BOS4.ALTER.NET (152.63.17.105) 18.908 ms 19.030 ms > 19.062 ms > 6 0.so-7-0-0.XL4.NYC4.ALTER.NET (152.63.17.97) 23.822 ms 17.608 ms > 17.729 ms > 7 0.ge-4-3-0.BR3.NYC4.ALTER.NET (152.63.3.122) 25.352 ms 27.370 ms > 27.457 ms > 8 if-13-2.icore1.NTO-NewYork.teleglobe.net (209.58.26.21) 25.067 ms > 25.099 ms * > 9 216.6.97.65 (216.6.97.65) 24.748 ms > > Here are the results of Dig to Verizon.net > jmkramer@till:~$ dig verizon.net > > ; <<>> DiG 9.4.1-P1 <<>> verizon.net > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6125 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;verizon.net. IN A > > ;; ANSWER SECTION: > verizon.net. 3051 IN A 206.46.232.39 > > ;; Query time: 103 msec > ;; SERVER: 85.255.115.99#53(85.255.115.99) > ;; WHEN: Sat Dec 22 08:05:44 2007 > ;; MSG SIZE rcvd: 45 > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > Discuss mailing list > [hidden email] > http://lists.blu.org/mailman/listinfo/discuss >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |