nzbget Docker fails connecting to any news server unless use IP addr: Could not resolve hostname

Hi - Hope I picked the right sub-forum for this. Just did a clean install of OMV5 and installed Docker for nzbget using pretty much the same parameters used for the same container in OMV4. Only some paths changed.

I have 3 news servers configured in nzbget and every one of them fails if I use their regular domain names, but succeed if I use their corresponding IP address. This leads me to think it's a DNS issue. But I think DNS is configured properly. I have tried the Cloudfare DNS (1.1.1.1) and google (8.8.8.8). Makes no difference.

root@omv:~# host news.usenetserver.com
news.usenetserver.com is an alias for usa.na.news.geo.usenetserver.com.
usa.na.news.geo.usenetserver.com is an alias for news.iad.usenetserver.com.
news.iad.usenetserver.com has address 69.16.179.27
news.iad.usenetserver.com has address 69.16.179.26
root@omv:~#

I've put in a ticket to Usenetserver but I'm not expecting a lot of help. It's not really their problem, just verifying configuration with them.

Any ideas?

Thanks,

Mark M.

PS: I did find one fairly recent posting about DNS problems but unfortunately I can't read German.

root@omv:~# docker exec -it nzbget /bin/bash

root@omv:/# cat /etc/resolv.conf

nameserver 1.1.1.1

nameserver 1.0.0.1

nameserver 192.168.50.1

root@omv:/#

(identical result outside of container)

root@omv:~# docker exec -it nzbget /bin/bash
root@omv:/# nslookup news.usenetserver.com
Server:         1.1.1.1
Address:        1.1.1.1:53

Non-authoritative answer:
news.usenetserver.com   canonical name = usa.na.news.geo.usenetserver.com
usa.na.news.geo.usenetserver.com        canonical name = news.iad.usenetserver.com
Name:   news.iad.usenetserver.com
Address: 69.16.179.26
Name:   news.iad.usenetserver.com
Address: 69.16.179.27

Non-authoritative answer:
news.usenetserver.com   canonical name = usa.na.news.geo.usenetserver.com
usa.na.news.geo.usenetserver.com        canonical name = news.iad.usenetserver.com

root@omv:/# exit
exit
root@omv:~# nslookup news.usenetserver.com
Server:         1.1.1.1
Address:        1.1.1.1#53

Non-authoritative answer:
news.usenetserver.com   canonical name = usa.na.news.geo.usenetserver.com.
usa.na.news.geo.usenetserver.com        canonical name = news.iad.usenetserver.com.
Name:   news.iad.usenetserver.com
Address: 69.16.179.26
Name:   news.iad.usenetserver.com
Address: 69.16.179.27

root@omv:~#

Thanks for the tip re translator, I should have thought of that! Duh! I checked out Update does not work - DNS problem and at the very bottom found this:

I answer to myself:

after reading the test thread again, I noticed a configuration change that I had to make earlier in a different context because a similar problem had occurred. The bug was then under OMV 2.0.x and has apparently persisted until today.

You have to do the following:

echo "nameserver 8.8.8.8" >> /etc/resolvconf/resolv.conf.d/tail

You can also enter other servers instead of the Google DNS server; I once tried the DNS servers from Open-DNS, they also work the same way. You can also edit the file /etc/resolvconf/resolv.conf.d/tail with WinSCP ...

and then restart the server.

root@omv:/etc/resolvconf# echo "nameserver 1.1.1.1" >> /etc/resolvconf/resolv.conf.d/tail
-bash: /etc/resolvconf/resolv.conf.d/tail: No such file or directory
root@omv:/etc/resolvconf# echo "nameserver 1.1.1.1" >> /etc/resolvconf/resolv.conf.d
root@omv:/etc/resolvconf#

root@omv:~# cat /etc/resolvconf/resolv.conf.d
nameserver 1.1.1.1
root@omv:~#

I rebooted and it works!! If you could explain what the heck is happening here I'd really appreciate it!

Also if you could please explain how the DNS setting in my router works with or against the OMV DNS setting. I haven't changed the router setting since I can't remember when.

Thanks so much for your help! I don't know what I'd do without this forum.

Thanks again, you're invaluable to OMV support!

Update 6/9/20 (final update): Tried re-installing OMV5 on my backup server and none of these problems appeared. So that's a clue. Did another fresh install of OMV5 on my production server and boom! all my difficulties vanished. Can't explain it. Just updating this note in case someone runs into similar problems. Wish I could give a more definitive answer as to what was fixed by starting over.

Update 6/7/20: Turns out the attempt to alter contents of /etc/resolvconf was wrong-headed. OMV5 uses systemd-resolvd not resolvconf. There were therefore no contents in /etc/resolvconf which is why my initial

echo "nameserver 1.1.1.1" >> /etc/resolvconf/resolv.conf.d/tail

failed and my subsequent clueless

echo "nameserver 1.1.1.1" >> /etc/resolvconf/resolv.conf.d

apparently worked but actually accomplished nothing. Can't explain why these steps seemed to fix domain resolution (briefly). Hallucinations?

Tried the fix here: SOLVED Upgrade from OMV 4 to OMV5

sudo systemctl disable systemd-resolved.service
systemctl stop systemd-resolved.service
sudo rm /etc/resolv.conf
sudo vi /etc/resolv.conf
nameserver 8.8.8.8
systemctl start systemd-resolved.service
sudo systemctl enable systemd-resolved.service

.. using both 1.1.1.1 and 8.8.8.8; still no joy.

===

6/6/2020:

Sadly, failing again with exact same DNS issue. Can't explain how it could revert; perhaps I rebooted? Not that that explains anything.

Well, I for one am putting this on the back burner. I have another machine running OMV4 that has none of these issues and will use it for this sort of network access (NzbGet, etc.) until I feel ready to start pulling hair out again.

I'm just leaving this dispiriting note so no one is disappointed that the fix shown here doesn't last. For now.