Hi! I’ve been happily using your DNS service for a month now but… I realized, just a few days ago, that only 1.0.0.1 is working now (greatly!) and correctly answering to requests.
I also noticed that the browser doesnt receive any data when accessing 1.1.1.1 website, while 1.0.0.1 shows the site correctly. Onestly I’m not sure if the requests were working fine on 1.1.1.1 BUT I am sure that the site 1.1.1.1 was displaying correctly from the same network (home) using the same browser (Firefox Quantum) a month ago…
Here some basic tests results.
C:\Users\mail>nslookup -class=chaos -type=txt id.server 1.1.1.1
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 1.1.1.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Tempo scaduto per la richiesta a UnKnown
Risposta da un server non autorevole:
id.server text =
"fco01"
C:\Users\mail>nslookup example.com 1.1.1.1
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 1.1.1.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Tempo scaduto per la richiesta a UnKnown
Sure!
In front of my pfsense there is a fritzbox acting as vdsl modem and pfsense is set as an “exposed host”… on LAN side just a switch and some WAPs.
1 1 ms 1 ms 1 ms pfSense.familynet.home [192.168.1.75]
2 2 ms 3 ms 2 ms modem.familynet.home [192.168.0.1]
3 20 ms 17 ms 7 ms 10.7.3.76
4 8 ms 6 ms 6 ms 10.7.30.38
5 9 ms 6 ms 6 ms 10.250.23.194
6 21 ms 20 ms 20 ms 10.3.144.86
7 19 ms 21 ms 19 ms 10.3.144.86
8 21 ms 20 ms 20 ms 1dot1dot1dot1.Cloudflare-dns.com [1.1.1.1]
1 1 ms 1 ms 1 ms pfSense.familynet.home [192.168.1.75]
2 3 ms 2 ms 4 ms modem.familynet.home [192.168.0.1]
3 6 ms 7 ms 6 ms 10.7.3.76
4 8 ms 5 ms 5 ms 10.7.30.46
5 8 ms 7 ms 28 ms 10.250.23.194
6 17 ms 21 ms 20 ms 10.254.1.69
7 19 ms 16 ms 16 ms 89.97.200.201
8 37 ms 34 ms 16 ms 89.97.200.69
9 16 ms 16 ms 16 ms Cloudflare-nap.namex.it [193.201.28.33]
10 25 ms 20 ms 20 ms 1dot1dot1dot1.Cloudflare-dns.com [1.0.0.1]
Tracing route to 1.1.1.1 [1dot1dot1dot1.Cloudflare-dns.com] on port 443
Over a maximum of 30 hops.
1 3 ms 4 ms 4 ms 192.168.1.75 [pfSense.familynet.home]
2 3 ms 4 ms 4 ms 192.168.0.1 [modem.familynet.home]
3 8 ms 8 ms 24 ms 10.7.3.76
4 10 ms 9 ms 9 ms 10.7.30.38
5 10 ms 8 ms 10 ms 10.250.18.25
6 9 ms 9 ms 10 ms 10.250.19.1
7 9 ms 12 ms 8 ms 10.250.23.194
8 26 ms 21 ms 22 ms 10.3.144.86
9 24 ms 24 ms 23 ms 10.3.144.86
10 Destination Reached in 40 ms. Port closed on 1.1.1.1
Trace Complete.
Tracing route to 1.0.0.1 [1dot1dot1dot1.Cloudflare-dns.com] on port 443
Over a maximum of 30 hops.
1 3 ms 8 ms 4 ms 192.168.1.75 [pfSense.familynet.home]
2 3 ms 3 ms 4 ms 192.168.0.1 [modem.familynet.home]
3 8 ms 9 ms 21 ms 10.7.3.76
4 8 ms 9 ms 8 ms 10.7.104.190
5 11 ms 11 ms 14 ms 10.250.18.25
6 10 ms 9 ms 9 ms 10.250.19.1
7 9 ms 13 ms 13 ms 10.250.23.194
8 21 ms 19 ms 17 ms 10.254.1.69
9 26 ms 19 ms 23 ms 89.97.200.197
10 81 ms 19 ms 18 ms 89.97.200.69
11 18 ms 19 ms 18 ms 193.201.28.33 [Cloudflare-nap.namex.it]
12 Destination Reached in 23 ms. Connection established to 1.0.0.1
Trace Complete.
I’ve asked our network team to reach out to Fastweb. Hopefully, they will be able to fix this. In the meantime, if your internet connection is IPv6 enabled, you can use 2606:4700:4700::1111 and 2606:4700:4700::1001