Everything seems to be working OK, does the DNS: ERROR: Could not reach DNS server: lookup resolver-check.u.channelsdvr.net: i/o timeout error matter if there are no apparent issues?
This is on synology running the synology package. Pinging that URI from an ssh session works just fine on the synology.
I note setting the server in an nslookup to resolver-check.u.channelsdvr.net does ineeded result in a timeout. Is this server a DNS resolver or something else?
This name - resolver-check.u.channelsdvr.net - should show your own DNS server IP address
https://dnschecker.org/#A/resolver-check.u.channelsdvr.net
It resolves to an address of my ISP (not to my own DNS server) interesingly this address is not one of the DNS servers that Ziply (wholesail networks) generally publishes or we use as upstream resolvers (i missed that it wasn't a channels endpoint, thanks for pointing that out) and this server does not seem to respond on port 53.
so i can only guess whatever this A record and diag check does, it is not working correctly, and is pointing to something that isn't a resolver. This doesn't seem to be causing any DNS issues so i won't worry about it.
alexb@SYN02:~$ sudo ping resolver-check.u.channelsdvr.net
Password:
PING resolver-check.u.channelsdvr.net (107.191.238.157) 56(84) bytes of data.
64 bytes from resolver1-bothwaxb.dns.as20055.net (107.191.238.157): icmp_seq=1 ttl=59 time=0.693 ms
64 bytes from resolver1-bothwaxb.dns.as20055.net (107.191.238.157): icmp_seq=2 ttl=59 time=0.548 ms
64 bytes from resolver1-bothwaxb.dns.as20055.net (107.191.238.157): icmp_seq=3 ttl=59 time=0.569 ms
64 bytes from resolver1-bothwaxb.dns.as20055.net (107.191.238.157): icmp_seq=4 ttl=59 time=0.550 ms
64 bytes from resolver1-bothwaxb.dns.as20055.net (107.191.238.157): icmp_seq=5 ttl=59 time=0.560 ms
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.