SABnzbd Forums

Looking for some PD Guidance. Sorry for this being cryptic, I can't post anything with a period or it says it's a link and I'm too new to do that.

Updated my container linuxserver/sabnzbd to 3.5.3 and now it can't resolve dognzb-dot-cr anymore.

/etc/resolv.conf looks like all my other containers

from inside the container:
* ping fails with bad address
* ping with the IP address 100% packet loss
* traceroute to IP does succeed!
* nslookup didn't work when it was the site alone, but when I added the docker nameserver as the source it does resolve

Tried deleting the container and re-pulling, no change. Not even sure what to try. All other containers and OS resolve and work properly - just Sab.

DNS problem?

In SABnzbd's upper right corner, click on the wrench symbol ("Status and interface options"), then click on first tab Status, and there click on the Refresh Arrow. What is the info in the upper part?

Yeah, I think it was a DNS problem. I am not sure what exactly was happening but a combination fo restarting the DNS servers and then restarting the container and the VM multiple times seems to have shaken something loose and now it's working.

Very Bizarre.