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

sloj

sloj

Disconnected
Messages
1,754
Location
Guwahati
ISP
BSNL
Anybody noticed BSNL changed the dns servers. It's 61.1.1.1 and 61.0.2.2 for me now and the pings to these are really slow, like minimum 20 ms and 50ms respectively.
 
Update - Looks like if the IP is in 117 series the DNS servers are 218.248.112.225 and 218.248.112.193, and if IP is in 59 series the DNS servers are 61.1.1.1 and 61.0.2.2.
 
For me, whether it's 59.x.x.x or 117.x.x.x, the BSNL DNS resolvers are always 218.248.112.65 & 218.248.112.97

Code: 
root@bumblebee:/tmp/log# ping -c 2 218.248.112.65
PING 218.248.112.65 (218.248.112.65): 56 data bytes
64 bytes from 218.248.112.65: seq=0 ttl=252 time=14.396 ms
64 bytes from 218.248.112.65: seq=1 ttl=252 time=14.342 ms

--- 218.248.112.65 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 14.342/14.369/14.396 ms
root@bumblebee:/tmp/log# ping -c 2 218.248.112.97
PING 218.248.112.97 (218.248.112.97): 56 data bytes
64 bytes from 218.248.112.97: seq=0 ttl=252 time=2.359 ms
64 bytes from 218.248.112.97: seq=1 ttl=252 time=1.917 ms

--- 218.248.112.97 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 1.917/2.138/2.359 ms
root@bumblebee:/tmp/log#
 
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?
 
Here too..getting the same DNS

varkey said:
For me, whether it's 59.x.x.x or 117.x.x.x, the BSNL DNS resolvers are always 218.248.112.65 & 218.248.112.97

Code: 
root@bumblebee:/tmp/log# ping -c 2 218.248.112.65
PING 218.248.112.65 (218.248.112.65): 56 data bytes
64 bytes from 218.248.112.65: seq=0 ttl=252 time=14.396 ms
64 bytes from 218.248.112.65: seq=1 ttl=252 time=14.342 ms

--- 218.248.112.65 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 14.342/14.369/14.396 ms
root@bumblebee:/tmp/log# ping -c 2 218.248.112.97
PING 218.248.112.97 (218.248.112.97): 56 data bytes
64 bytes from 218.248.112.97: seq=0 ttl=252 time=2.359 ms
64 bytes from 218.248.112.97: seq=1 ttl=252 time=1.917 ms

--- 218.248.112.97 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 1.917/2.138/2.359 ms
root@bumblebee:/tmp/log#
Click to expand...
 

Screenshot_20200521-073539__01.webp


I always get ip in 117 series in fiber, on adsl it varied but the dns remains the same.
 
arunkadambanattu said:
Here too..getting the same DNS
Click to expand...


Yes , I too get 218.248.112.65 & 218.248.112.97.
Right now I am on 59.x.x.x IP series.

Ping to 61.1.1.1 :

Code: 
pi@raspberrypi:~ $ ping 61.1.1.1
PING 61.1.1.1 (61.1.1.1) 56(84) bytes of data.
64 bytes from 61.1.1.1: icmp_seq=1 ttl=252 time=1.48 ms
64 bytes from 61.1.1.1: icmp_seq=2 ttl=252 time=2.09 ms
64 bytes from 61.1.1.1: icmp_seq=3 ttl=252 time=1.63 ms
64 bytes from 61.1.1.1: icmp_seq=4 ttl=252 time=1.93 ms
64 bytes from 61.1.1.1: icmp_seq=5 ttl=252 time=2.08 ms
64 bytes from 61.1.1.1: icmp_seq=6 ttl=252 time=1.89 ms
64 bytes from 61.1.1.1: icmp_seq=7 ttl=252 time=2.05 ms
64 bytes from 61.1.1.1: icmp_seq=8 ttl=252 time=1.88 ms
64 bytes from 61.1.1.1: icmp_seq=9 ttl=252 time=2.06 ms
64 bytes from 61.1.1.1: icmp_seq=10 ttl=252 time=2.22 ms
64 bytes from 61.1.1.1: icmp_seq=11 ttl=252 time=1.70 ms
64 bytes from 61.1.1.1: icmp_seq=12 ttl=252 time=2.12 ms
^C
--- 61.1.1.1 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 26ms
rtt min/avg/max/mdev = 1.475/1.926/2.215/0.215 ms
 
Ping report -
Code: 
$ ping -c 4 61.1.1.1
PING 61.1.1.1 (61.1.1.1) 56(84) bytes of data.
64 bytes from 61.1.1.1: icmp_seq=1 ttl=250 time=23.3 ms
64 bytes from 61.1.1.1: icmp_seq=2 ttl=250 time=62.6 ms
64 bytes from 61.1.1.1: icmp_seq=3 ttl=250 time=27.5 ms
64 bytes from 61.1.1.1: icmp_seq=4 ttl=250 time=26.4 ms

--- 61.1.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time
3005ms
rtt min/avg/max/mdev = 23.390/35.021/62.671/16.037 ms
$ ping -c 4 61.0.2.2
PING 61.0.2.2 (61.0.2.2) 56(84) bytes of data.
64 bytes from 61.0.2.2: icmp_seq=1 ttl=249 time=35.5 ms
64 bytes from 61.0.2.2: icmp_seq=2 ttl=249 time=35.5 ms
64 bytes from 61.0.2.2: icmp_seq=3 ttl=249 time=44.1 ms
64 bytes from 61.0.2.2: icmp_seq=4 ttl=249 time=36.6 ms

--- 61.0.2.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time
3006ms
rtt min/avg/max/mdev = 35.524/37.973/44.146/3.601 ms
$ ping -c 4 218.248.112.193
PING 218.248.112.193 (218.248.112.193) 56(84) bytes of d
ata.
64 bytes from 218.248.112.193: icmp_seq=1 ttl=250 time=2
8.9 ms
64 bytes from 218.248.112.193: icmp_seq=2 ttl=250 time=2
2.3 ms
64 bytes from 218.248.112.193: icmp_seq=3 ttl=250 time=2
7.5 ms
64 bytes from 218.248.112.193: icmp_seq=4 ttl=250 time=2
6.6 ms

--- 218.248.112.193 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time
3006ms
rtt min/avg/max/mdev = 22.390/26.376/28.989/2.457 ms
$ ping -c 4 218.248.112.225
PING 218.248.112.225 (218.248.112.225) 56(84) bytes of d
ata.
64 bytes from 218.248.112.225: icmp_seq=1 ttl=251 time=1
4.3 ms
64 bytes from 218.248.112.225: icmp_seq=2 ttl=251 time=1
4.9 ms
64 bytes from 218.248.112.225: icmp_seq=3 ttl=251 time=1
5.1 ms
64 bytes from 218.248.112.225: icmp_seq=4 ttl=251 time=1
5.2 ms

--- 218.248.112.225 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time
3006ms
rtt min/avg/max/mdev = 14.397/14.950/15.276/0.335 ms
$ ping -c 4 218.248.112.65
PING 218.248.112.65 (218.248.112.65) 56(84) bytes of dat
a.
64 bytes from 218.248.112.65: icmp_seq=1 ttl=250 time=49
.1 ms
64 bytes from 218.248.112.65: icmp_seq=2 ttl=250 time=43
.9 ms
64 bytes from 218.248.112.65: icmp_seq=3 ttl=250 time=46
.1 ms
64 bytes from 218.248.112.65: icmp_seq=4 ttl=250 time=51
.4 ms

--- 218.248.112.65 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time
3006ms
rtt min/avg/max/mdev = 43.945/47.682/51.478/2.879 ms
$ ping -c 4 218.248.112.97
PING 218.248.112.97 (218.248.112.97) 56(84) bytes of dat
a.
64 bytes from 218.248.112.97: icmp_seq=1 ttl=249 time=65
.9 ms
64 bytes from 218.248.112.97: icmp_seq=2 ttl=249 time=65
.9 ms
64 bytes from 218.248.112.97: icmp_seq=3 ttl=249 time=65
.6 ms
64 bytes from 218.248.112.97: icmp_seq=4 ttl=249 time=65
.7 ms

--- 218.248.112.97 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time
3006ms
rtt min/avg/max/mdev = 65.633/65.842/65.974/0.344 ms
$
 

Similar threads

Protector
IPv4 vs IPv6 Difference
Replies
0
Views
258
Protector
guywithproblems
How can I change DNS Server for BSNL, they are really bad on Default.
Replies
6
Views
1,967
Ajay15
sahshivam
Jio bad routing to Vultr Delhi Servers
Replies
3
Views
1,044
Lolita_Magnum
M
New Fiber from BSNL - Doubts about login details
Replies
3
Views
1,433
alfiabraham
Top