Could not reach DNS server: lookup resolver-check.u.channelsdvr.net: no such host

Channels DVR Server Troubleshooting
#1

Seeing this on all my servers when running Troubleshooting.
My DNS is working fine.
nslookup results

nslookup community.getchannels.com
Server:  UnKnown
Address:  192.168.1.1
Non-authoritative answer:
Name:    community.getchannels.com
Addresses:  104.21.71.35
          172.67.142.202

nslookup resolver-check.u.channelsdvr.net
Server:  UnKnown
Address:  192.168.1.1
*** UnKnown can't find resolver-check.u.channelsdvr.net: Non-existent domain

nslookup resolver-check.u.channelsdvr.net 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1
Non-authoritative answer:
Name:    resolver-check.u.channelsdvr.net
Address:  172.69.140.83

nslookup resolver-check.u.channelsdvr.net 8.8.8.8
Server:  dns.google
Address:  8.8.8.8
Non-authoritative answer:
Name:    resolver-check.u.channelsdvr.net
Address:  74.125.181.144

nslookup resolver-check.u.channelsdvr.net 9.9.9.9
Server:  dns9.quad9.net
Address:  9.9.9.9
Non-authoritative answer:
Name:    resolver-check.u.channelsdvr.net
Address:  74.63.16.249
#2

And now it's working :man_shrugging:

nslookup resolver-check.u.channelsdvr.net
Server:  UnKnown
Address:  192.168.1.1
Non-authoritative answer:
Name:    resolver-check.u.channelsdvr.net
Address:  172.70.205.39

ping resolver-check.u.channelsdvr.net
Pinging resolver-check.u.channelsdvr.net [172.70.205.39] with 32 bytes of data:
Reply from 172.70.205.39: bytes=32 time=25ms TTL=51
Reply from 172.70.205.39: bytes=32 time=24ms TTL=51
Reply from 172.70.205.39: bytes=32 time=27ms TTL=51
Reply from 172.70.205.39: bytes=32 time=26ms TTL=51
Ping statistics for 172.70.205.39:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 27ms, Average = 25ms
#3

Looks like somebody forgot to update ipdns1.channelsdvr.net and ipdns2.channelsdvr.net

They claim the authority for u.channelsdvr.net is ns{1..4}.dnsimple.com.

$ dig u.channelsdvr.net ns @ipdns1.channelsdvr.net. +short

ns1.dnsimple.com.
ns2.dnsimple.com.
ns3.dnsimple.com.
ns4.dnsimple.com.

The record in question (no longer?) exists on these servers.

Oooops ......

Probably the record overlooked during the (recent?) migration of the authoritative servers.

Dejavu:

#4

Quad9 is having problems resolving the name as well (it worked earlier):

$ dig resolver-check.u.channelsdvr.net @9.9.9.9

; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> resolver-check.u.channelsdvr.net @9.9.9.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38430
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;resolver-check.u.channelsdvr.net. IN   A

;; AUTHORITY SECTION:
u.channelsdvr.net.      232     IN      SOA     ns1.dnsimple.com. admin.dnsimple.com. 1583056184 86400 7200 604800 300

;; Query time: 12 msec
;; SERVER: 9.9.9.9#53(9.9.9.9) (UDP)
;; WHEN: Thu Sep 25 14:24:34 PDT 2025
;; MSG SIZE  rcvd: 119
#5

Please try if this build is any better for you:

#6

It might take awhile to know if that fixes it.
It's working right now and I only noticed it because I ran Troubleshooting.
Fortunately I don't have to do that often.

#7

Looks like the name resolver-check.u.channelsdvr.net has been retired and is no longer checked.

1 Like