Slow DNS issues
Forums › Service Issues › Networking, Routing, Technology › Slow DNS issues
-
Somehow I woke up to the DNS not working.
I’ve removed the network configuration on my macbook, restarted, set it up again but something is wrongPING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=57 time=16.379 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=21.031 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=14.701 ms— 1.1.1.1 ping statistics —
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 14.701/17.370/21.031/2.678 ms
@MacBook-Pro-2 ~ % ping -c 3 8.8.8.8PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=114 time=37.074 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=36.766 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=114 time=42.414 ms— 8.8.8.8 ping statistics —
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 36.766/38.751/42.414/2.593 ms
@MacBook-Pro-2 ~ % ping -c 3 185.228.168.10PING 185.228.168.10 (185.228.168.10): 56 data bytes
64 bytes from 185.228.168.10: icmp_seq=0 ttl=52 time=262.749 ms
64 bytes from 185.228.168.10: icmp_seq=1 ttl=52 time=288.216 ms
64 bytes from 185.228.168.10: icmp_seq=2 ttl=52 time=310.623 ms— 185.228.168.10 ping statistics —
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 262.749/287.196/310.623/19.558 ms
@MacBook-Pro-2 ~ % nslookup -type=txt iptest.whois.dnscontest.cleanbrowsing.org 185.228.168.10Server: 185.228.168.10
Address: 185.228.168.10#53Non-authoritative answer:
iptest.whois.dnscontest.cleanbrowsing.org text = “CleanBrowsing Whois: Datacenter: dns-edge-usa-west-la-c, Destination:185.228.168.10, ClientIP: 49.228.237.4”Authoritative answers can be found from:
@MacBook-Pro-2 ~ % nslookup -q=TXT mylocation.whois.dnscontest.cleanbrowsing.orgServer: 2405:9800:a:1::12
Address: 2405:9800:a:1::12#53** server can’t find mylocation.whois.dnscontest.cleanbrowsing.org: NXDOMAIN
MacOS
Macs come with the networksetup command line tool that allows you to configure the network settings. It can also be used to change the nameservers by using it with the -setdnsservers flag. Open your terminal by going to the spotlight and typing “terminal” and run:sudo networksetup -setdnsservers Wi-Fi 185.228.168.168
That will force the Wi-Fi to go through CleanBrowsing (185.228.168.168). If it works, you won’t get any warning or error in the terminal and you are all set. As a bonus point, you can run the chflags command to block anyone from changing the nameserver via the graphical user interface:sudo chflags schg /Library/Preferences/SystemConfiguration/preferences.plist
This worked better. Seems to be the app that is causing issues
Where are you located and your ISP? Mind sending the output of:
traceroute 185.228.168.10
ortracert 185.228.168.10 (if you are on windows).
So we can see what is going on? And the other results means you are going through IPv6, not the configured IPv4 DNS.
You must be logged in to reply to this topic.