Forum Discussion

rwf86's avatar
rwf86
Friendly Neighbour
1 month ago

Secondary DNS Server not working

Hello, the secondary DNS servers pushed to the router by DHCP are not working, both for IPv4 and IPv6. This has been ongoing for a while.

The above is captured from the router.

Pinging 75.153.171.116 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 75.153.171.116:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Pinging 2001:568:ff09:10a::116 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2001:568:ff09:10a::116:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Telus should not push DNS servers that are not working.

Roger

4 Replies

  • It may well be the case that DNS servers are blocked from replying to ping, but the test shown by the OP is being done by the Telus-supplied router. If the secondary DNS servers are being blocked from replying to ping, why are they being tested by the Telus-supplied router using ping?

  • FuzzyLogic's avatar
    FuzzyLogic
    Icon for Community Power User rankCommunity Power User

    It's not unusual for DNS servers to block pings so that they are more responsive to DNS lookups. As mentioned you can do a test by querying the DNS directly.

  • rwf86's avatar
    rwf86
    Friendly Neighbour

    Ah, using nslookup works on the secondary DNS server (and also Resolve-DnsName for the secondary IPv6 server).

    However, it is greatly misleading that the router (diagnostic) shows that the secondary server is not responding (as shown in the image in the first message).

    I think Telus needs to enable ping on those secondary DNS servers.

  • TELUS_Support's avatar
    TELUS_Support
    Icon for Official Support Team rankOfficial Support Team

    Instead of using a standard ping, the best way to verify if your secondary DNS is actually failing is to force a direct DNS lookup against it using nslookup in your command prompt:

     

    nslookup google.com 75.153.171.116

     

    If this returns an IP address for Google, the server's healthy and actively working, despite ignoring standard ping requests. Give that a try and let us know what results you get.