BSNL's new DNS Servers: 61.0.1.1, 61.0.2.2, 61.0.3.3, 61.1.1.1

Did DNS Benchmark 6 times, with different IP on Fibernet.



What is more relevant Cached, Uncached & DotCom?

If we don't consider security or privacy at all, does this mean BSNL DNS is better ?

I just want the best ping time, is'nt BSNL better that 1.1.1.1 & Google DNS ?

sloj said:

Then I guess it's safe to say that it's region based. How is the ping to 61.1.1.1 and 61.0.2.2 though?

Click to expand...

Nope I did get those ip once...

If i do an ipconfig /all . It shows my DNS to be
DNS Servers . . . . . . . . . . . : 61.1.1.1
61.0.1.1

But when I check it online I get.

The New BSNL Servers support Anycast routing capability which kinda speeds up the DNS. Glad BSNL is trying to keep up with standard protocols

Ameen said:

Nope I did get those ip once...

Click to expand...

A reply almost 3 months later. 😛

@sloj better late than never 😁😁

I'm getting these

Same

From my ISP in Mumbai, ping to google is still better... and 1.1.1.1 is even better with 1 ms !
ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=2ms TTL=119
Reply from 8.8.8.8: bytes=32 time=2ms TTL=119
Reply from 8.8.8.8: bytes=32 time=2ms TTL=119
Reply from 8.8.8.8: bytes=32 time=2ms TTL=119

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

ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=1ms TTL=60
Reply from 1.1.1.1: bytes=32 time=1ms TTL=60
Reply from 1.1.1.1: bytes=32 time=1ms TTL=60
Reply from 1.1.1.1: bytes=32 time=1ms TTL=60

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

@popcorn How are u getting 1ms to 1.1.1.1 . I mean the first router hop will itself takes 1ms right?

1st hop is usually <1ms on wire but thats still a very low ping. @popcorn Can you a traceroute to 1.1.1.1

I have two layers in my private routers still getting 1ms to 1.1.1.1
tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.220.1
2 <1 ms <1 ms <1 ms 192.168.210.1
3 1 ms 1 ms 1 ms 172.20.0.1
4 2 ms 2 ms 1 ms as13335.bom.extreme-ix.net [103.77.108.118]
5 1 ms 1 ms 1 ms one.one.one.one [1.1.1.1]

Trace complete.

tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.220.1
2 <1 ms <1 ms <1 ms 192.168.210.1
3 1 ms 1 ms 1 ms 172.20.0.1
4 2 ms 2 ms 2 ms 72.14.195.30
5 2 ms 2 ms 1 ms 209.85.247.65
6 4 ms 3 ms 2 ms 216.239.47.149
7 2 ms 1 ms 1 ms dns.google [8.8.8.8]

Trace complete.

How is it possible, there are various factors affecting it isn't it? Like router congestion and all.

Mumbai ISPs have excellent peering for Cloudflare and many other sites due to Extreme IX.

I setup Linode VPS in Mumbai and pings to CF were sub 1ms (ofc it's in a DC but still)

Did a DNS test and found open dns fast , changed it and found it was so fast.. Was using google DNS which was horrible.. i dont know why. BSNL interfering ?

Anyway added BSNL own dns server ip and found it was much faster on benchmark , but dont want to use them for now. I dont have that much trust on them.