Synology DVR not recording

[rb9999]

I am not able to get the Synology DVR recording working on my HDHomeRun Quatro. I have an open ticket and I have gotten a few suggestions via email and tried them all and it is still not working. I am only getting responses every few days or so and got 1 call while I was away. So I am not getting anywhere with support. I have done a lot of digging with AI models on this and have gotten nowhere as well.

I have a Synology DS220+ and installed the Synology package. For some time I had the setting on my NVIDIA shield set to record to this device and my programs were recording to my attached hard drive. When I realized this I started trying to get the NAS functionality to work. I made sure all and any HDHOMERUN apps I had did not have this option checked which was one of their suggestions. Didn't fix it. I got another suggestion that I was using 2 interfaces on my NAS, so my NAS had 2 IP addresses. They said remove one of them and assign the unused interface to use DHCP. So I did that and unplugged one of the lan cables. So now I only have one NAS IP. I am seeing issues in the log to dns failures. I made sure my DNS for my interface is 1.1.1.1 and 1.0.0.1 on both the one interface (this setting only allows 1 ip) and in CONTROL PANEL-NETWORK. I am still having this issue.

Here is part of my log:
20250729-17:10:32 Recorded: recorded sync to record-api.hdhomerun.com
20250729-17:10:32 Recording: event download from record-api.hdhomerun.com
20250729-17:10:32 Recording: myhdhomerun_files webclient error 2 dns failed
20250729-17:10:32 Recorded: recorded sync failed
20250729-17:10:32 Recording: myhdhomerun_record webclient error 2 dns failed
20250729-17:10:32 Recording: event download failed
20250729-17:10:32 Recording: disk space available = 11734GB
20250729-17:10:32 Recording: current time = Tue Jul 29 17:10:32 2025 (correction of 0s)
20250729-17:10:32 Recording: no timer events planned
20250729-17:10:32 Recording: 107B6CA0 lineup request success (found 46 channels)

I can hit my record engine at 192.168.86.34:50000 and I see this:
System Status
Version 20250506
Storage ID 30F55926-DD8C-642E-6475-BEBE5B6348AC
Record Path /volume1/HDHomeRun/
Search Path /volume1/HDHomeRun/
Free Space 11733 GB
IP Address 192.168.86.34
IP Address 172.17.0.1
IP Address [fe80::42:95ff:fe2e:935e]
IP Address 172.20.0.1
IP Address [fe80::42:6ff:fe35:c61d]
IP Address [fe80::587a:d7ff:feed:d973]
IP Address [fe80::700f:a1ff:fe9b:6f71]
IP Address [fe80::bcca:95ff:fe39:4bc5]
IP Address [fe80::c417:88ff:fe66:9831]
IP Address [fe80:97ff:fe9b:4d4a]
IP Address [fe80:54ff:fe05:bee6]
IP Address [fe80:f6ff:fe5f:2208]
IP Address [fe80::b4a6:91ff:fe65:4ecd]

I have uninstalled the synology package multiple times, I have uninstalled reinstalled the Android app and I get nothing.

Any and all suggestions appreciated.

[signcarver]

I would double check gateway address, and probably turn dhcp on both interfaces as a test.

I have heard recently of an isp blocking 1.1.1.1 recently for dns as a quick resolution to configuration issues they had earlier this month and have also heard of some isp devices getting switched to require isp's dns in the past few months (such feature can usually be turned off).

Which package is it? If it is the docker one, I would look at how that is configured. I'd also look at any firewall that may also be configured (either on synology or between it and gateway (router)).

[rb9999]

I checked the gateway address and made some modifications and ensured it was using 1.1.1.1 with nslookup and it was using 1.1.1.1. Unfortunately, I had the same issue. Same errors in the log (I can't confirm that these errors are the actual problem or not. I did the same thing again with 8.8.8.8 and it didn't work either.

I am using the official spk that Silicon Dust provides. I disabled my firewalls as well, still no luck.

[NedS]

Something is preventing the DVR on the NAS from communicating to our servers, but I see enough diagnostic data to know that the NAS can talk to the HDHomeRun, and the HDHomeRun is talking to our servers. Odd. I will try to find you an answer, maybe I can replicate the issue on my own Synology.

[rb9999]

Thanks.