1.1.1.1 DNS

H

HavocXphere

Honorary Master
Joined
Oct 19, 2007
Messages
33,153
Reaction score
1,297
Location
Europe
Anyone seeing DNS failures on 1.1.1.1?

Was running both 8.8.8.8 and 1.1.1.1. Removed the big brother and now I'm getting occasional resolution issues.

Just me?

I should add that I've been messing with a Rasp & Pi hole...but that was fine until I changed the above
 
HavocXphere said:
Anyone seeing DNS failures on 1.1.1.1?

Was running both 8.8.8.8 and 1.1.1.1. Removed the big brother and now I'm getting occasional resolution issues.

Just me?

I should add that I've been messing with a Rasp & Pi hole...but that was fine until I changed the above
Click to expand...
What is your ISP.

I have countless issues on Web Africa when I use 1.1.1.1
 
Not only am I not having issues with 1.1.1.1 with Cool Ideas, but my browsing is snappier than ever.
 
Using both 1.1.1.1 and 1.0.0.1 and no problems thus far, except for Vodacom and their network.
 
Slowly moving all my networks over to using 1.1.1.1 as a primary and 8.8.8.8 as secondary.
I do prefer to use the root servers but I have forwarders setup in case the Windows Server cant resolve the address. Smaller sites get the DNS treatment since I don't trust ISP DNS servers to be up 100%.
 
killerbyte said:
Slowly moving all my networks over to using 1.1.1.1 as a primary and 8.8.8.8 as secondary.
Click to expand...
Well that was my initial thinking...but the Rasp sends the bulk of the traffic to 8.8.8.8. Presumably it's closer to me. But I didn't want that cause big bro knows enough about me already
 
Bryn said:
Not only am I not having issues with 1.1.1.1 with Cool Ideas, but my browsing is snappier than ever.
Click to expand...

+1

1.1.1.1 works incredibly well on Cool Ideas... I wonder why it doesn't work with Crystal Web :wtf:
 
Waylander said:
+1

1.1.1.1 works incredibly well on Cool Ideas... I wonder why it doesn't work with Crystal Web :wtf:
Click to expand...
It sounds like the issue is that Cisco gear uses the IP for internal dashboards. Plus it's in an experimental IP range.

:/
 
C:\Users\>ping -a 8.8.4.4

Pinging google-public-dns-b.google.com [8.8.4.4] with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=2ms TTL=56
Reply from 8.8.4.4: bytes=32 time=2ms TTL=56
Reply from 8.8.4.4: bytes=32 time=2ms TTL=56
Reply from 8.8.4.4: bytes=32 time=2ms TTL=56
 
C:\Users\>ping -a 1.1.1.1

Pinging 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
HavocXphere said:
Well that was my initial thinking...but the Rasp sends the bulk of the traffic to 8.8.8.8. Presumably it's closer to me. But I didn't want that cause big bro knows enough about me already
Click to expand...
The assumption.
You should block access to the Google DNS on the router to prevent corrupting local DNS resolver cache.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X