Troubleshooting DNS issues

This is the error in the log - suspect it has something to do with all the DNS errors I get, which didn't even get corrected when I reset my router.

2024/02/01 23:07:58.729906 [SYS] Error checking for update: Get "https://channels-dvr.s3.amazonaws.com/prerelease.json": dial tcp: lookup channels-dvr.s3.amazonaws.com: no such host

That's exactly the issue. You need to get your DNS/network issues resolved. If you're using third-party DNS servers, proxies, VPN, etc., disable them.

No third-party DNS servers. I've tried everything I could think of to escape the DNS nightmare I've been dealing with ever since our son moved out of the house and took his computer off our home network. I had removed a PC that had been used as a a router running pfSense and returned to using our Netgear Nighthawk AX6 as our router. When I asked him about possible causes he mentioned having had several significant DDoS attacks, so I suspect our DNS problems stem from that somehow. I thought resetting the router to factory settings and setting it up all over again might help, but it seemed to make no difference. I've considered changing the MAC address of the router to try to get assigned a different external IP from the ISP, but I haven't gone that far yet because I don't know what ramification there may be.

What OS are you running your channels server on?

Windows 10 Pro

Go to a command prompt and run nslookup channels-dvr.s3.amazonaws.com
Post the result

It should say the dns server that it is trying use
(Whatever your machine is set to currently)

Then do an ipconfig /all
Post that result as well

Finally give me the ip address of your dns server that you are currently using .

Ill try and sort this for you if i get all of that info

That would be awesome if you can help me out of the DNS mess I've been in.

Here is the information you asked for.

C:\WINDOWS\system32>nslookup channels-dvr.s3.amazonaws.com
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
Name: s3-w.us-east-1.amazonaws.com
Addresses: 52.217.73.212
52.217.170.57
54.231.234.25
52.217.134.177
54.231.192.1
52.217.229.225
52.217.86.228
52.217.224.137
Aliases: channels-dvr.s3.amazonaws.com
s3-1-w.amazonaws.com

C:\WINDOWS\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : TLZ400
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : D4-85-64-B3-55-31
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.8(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, January 30, 2024 1:45:27 AM
Lease Expires . . . . . . . . . . : Saturday, February 3, 2024 1:45:26 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 4:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-NordVPN Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-F2-E2-4F-80
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-85-1D-6D-8D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter vEthernet (WSL):

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : 00-15-5D-6D-68-B7
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a32e:9275:623:574d%32(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.176.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 536876381
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-BE-55-8C-D4-85-64-B3-55-31
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

My Netgear Nighthawk Router is currently setup to use these DNS Servers:
Primary DNS 8.8.8.8
Secondary DNS 8.8.4.4

I should add that I've used Cloudflare WARP on a laptop and one of my PCs and the DNS errors stop, but any websites I visit don't recognize me, which can be quite inconvenient at times - so I usually keep it disabled.

Sorry - not sure how some of the above text became bolded.

I see you have Nord as well as HyperV for WSL.
Are you disconnected from Nord when you are having this issue?
Is the Channels server running as a docker container or natively on the PC?

Thanks for looking at this!

I'm not using Nord on that PC - just haven't uninstalled it yet. I also only used HyperV temporarily a few years back when I was looking for other alternatives to Windows Media Center as a DVR. Can they invite DNS errors when not in use?

The Channels server has been running as a service natively on that PC for about 6 months. Prior to that it was running as a standard application installed on the native OS.

Honestly I'm not sure what you have going on there. The nslookup was fine so whatever was going on before isn't going on now. If it happens again you could set your DNS statically on the NIC and see if that makes a difference.

You may also want to see what removing the custom/Google DNS servers from your router may do.

The first step to troubleshooting DNS is removing custom paths; see if it works with your ISP's DNS servers.

1 Like

Earlier today I was able to download the Pre-release, but I didn't install it at the time because I was recording several things I didn't want to interrupt. Since then it looks like a stable release was uploaded and that installed fine.

After, I changed my router to get the DNS from the ISP, so I'll try that again (it seemed to be less stable when I used that for awhile about a year ago).