Google Public DNS-over-TLS (dns.google)

  • Thread starter Thread starter m_k
  • Start date Start date
  • Replies Replies 53
  • Views Views 12,279
Nothing I know. Not at least with BSNL. I am using 3 rd party DNS since almost 2 years now. Never faced any issue because of not using BSNL DNS.

Thanks for the confirmation meetdilip, right now i am also using googledns without any problem
 
Always welcome 🙂
 
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 12 ms 13 ms 17 ms **.**.**.**
2 * 9 ms 8 ms **.**.**.**
3 9 ms 13 ms 19 ms **.**.**.**
4 9 ms 9 ms 15 ms 121.241.88.53.static-*********.vsnl.net.in [121.
241.88.53]
5 84 ms 27 ms 103 ms 121.243.28.62
6 19 ms 17 ms 19 ms 115.113.165.98.static-mumbai.vsnl.net.in [115.11
3.165.98]
7 23 ms 19 ms 29 ms 72.14.232.99
8 70 ms 28 ms 31 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.


IPs are replaced with * for security concern.

See the direct link from VSNL (Mumbai) to mountain view (Google Head quarter) 72.14.232.99. From mumbai(VSNL) to Google, data takes almost 10ms to reach.


Traced route from tikona.

----------

Post yours trace route here.
 
I dont think 10 ms is possible from mumbai to ca, if they laws of physics are to be believed.They are, I guess, using anycasting.
 
Code: 
Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation.  All rights reserved.C:\Users\Chaitanya>ping 8.8.8.8Pinging 8.8.8.8 with 32 bytes of data:Reply from 8.8.8.8: bytes=32 time=19ms TTL=57Reply from 8.8.8.8: bytes=32 time=19ms TTL=57Reply from 8.8.8.8: bytes=32 time=18ms TTL=57Reply from 8.8.8.8: bytes=32 time=18ms TTL=57Ping statistics for 8.8.8.8:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 18ms, Maximum = 19ms, Average = 18msC:\Users\Chaitanya>tracert 8.8.8.8Tracing route to google-public-dns-a.google.com [8.8.8.8]over a maximum of 30 hops:  1
 
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=99ms TTL=54
Reply from 8.8.8.8: bytes=32 time=106ms TTL=54
Reply from 8.8.8.8: bytes=32 time=95ms TTL=54
Reply from 8.8.8.8: bytes=32 time=104ms TTL=54

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 106ms, Average = 101ms

Not good!
 

Airtel in Chennai.

Code: 
C:\>tracert 8.8.8.8Tracing route to google-public-dns-a.google.com [8.8.8.8]over a maximum of 30 hops:  1
 
Not for me I guess

Code: 
Tracing route to google-public-dns-a.google.com [8.8.8.8]over a maximum of 30 hops:  1     3 ms     3 ms     1 ms  192.168.1.1  2     2 ms     1 ms     1 ms  192.168.1.1  3    14 ms    27 ms    12 ms  10.202.222.1  4    18 ms    11 ms    14 ms  119.82.80.1  5    11 ms     9 ms    10 ms  203.122.61.42  6    11 ms    10 ms     9 ms  72.14.222.2  7    13 ms    36 ms    13 ms  72.14.237.3  8    35 ms    31 ms    37 ms  google-public-dns-a.google.com [8.8.8.8]
 
This is with Reliance BB Trivandrum 🙁




The quality of service provided by Reliance is very pathetic. As days go on, all the heavy downloaders are jumping into the Reliance bandwagon because of the no FUP policies. This (I think) is what is reducing the overall reliability of the network. Too many users within the network who are trying to squeeze the very last ounce of bandwidth available.
 
From beam


I think Mine and bobby's is somewhat similar. It means beam and tikona buy bandwidth from VSNL. Our request go through the same server of VSNL 115.113.165.98 while rest of ISP's. As per mentioned above result, it cleared mention reliance (Trivandrum) and airtel route go through their own server having poor result than us. Very soon. I will post some popular site traced route.
If anybody has wimax, post their result. I think their results may be better than wired except beam. Wimax is just simple one mesh WLAN network. One main Access point is connected to optical fiber. So, there won't be more loss like outdated wireline in India.
 

Top