Attached are my network settings and dockers in UNraid as well as my (Tower) network from my router.

I can somewhow get DuckDNS working using -- 1.1.1.1. in advanced in the container under extra parameters and same for SWAG but I keep getting werrors and it will just not work. I tried to connect to google using:

root@Tower:~# nslookup google.com

;; communications error to 127.0.0.1#53: connection refused

;; communications error to 127.0.0.1#53: connection refused

;; communications error to 127.0.0.1#53: connection refused

Server: 149.***.112.11

Address: 149.***.112.11#53

Non-authoritative answer:

Name: google.com

Address: 172.217.12.110

;; communications error to 127.0.0.1#53: connection refused

;; communications error to 127.0.0.1#53: connection refused

;; communications error to 127.0.0.1#53: connection refused

Name: google.com

The above is what I get, so something is definitely broken and apparently has been for a looong time.
I am only now figuring this out since I wanted to share my Kavita book library with a friend and was trying to expose that container.
I have never exposed anything before so it is my first time trying to set things up, which led to me finding these errors.

this is the log for the SWAG container:

using keys found in /config/keys

Variables set:

PUID=99

PGID=100

TZ=America/Los_Angeles

URL=kavitalordshad0w.duckdns.org

SUBDOMAINS=www,

EXTRA_DOMAINS=

ONLY_SUBDOMAINS=true

VALIDATION=dns

CERTPROVIDER=

DNSPLUGIN=duckdns

EMAIL=perfects

STAGING=false

the resulting certificate will only cover the main domain due to a limitation of duckdns, ie. subdomain.duckdns.org

Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created

Using Let's Encrypt as the cert provider

E-mail address entered: perfects

Generating new certificate

Account registered.

Requesting a certificate for kavital.duckdns.org

Waiting 30 seconds for DNS changes to propagate

Successfully received certificate.

Certificate is saved at: /config/etc/letsencrypt/live/kavita.duckdns.org/fullchain.pem

Key is saved at: /config/etc/letsencrypt/live/kavita.duckdns.org/privkey.pem

This certificate expires on 2025-10-06.

These files will be updated when the certificate renews.

NEXT STEPS:

- The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https://certbot.org/renewal-setup for instructions.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

If you like Certbot, please consider supporting our work by:

* Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate

* Donating to EFF: https://eff.org/donate-le

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ERROR: Cert does not exist! Please see the validation error above. Make sure you entered correct credentials into the /config/dns-conf/duckdns.ini file.

this is my duckdns ini:

# Instructions: https://github.com/infinityofspace/certbot_dns_duckdns#credentials-file-or-cli-parameters
# Replace with your API token from your duckdns account.
dns_duckdns_token=*********-14a8-4c85-8ea3-5f9a24313351

Edited July 9, 20251 yr by LordShad0w
removal of personal info

I see you are using a UniFi router. Back a few years ago, I was using a Ubiquiti EdgeRouter X and had DNS problems in setting up the SSL certificate. Here are a couple of posts back from that time:

https://forums.unraid.net/topic/59845-unraid-os-version-640-rc8q-available/page/7/#comment-587753

and

https://forums.unraid.net/topic/61265-what-router-are-you-running/page/3/?tab=comments#comment-637221

The problem is basically explained here:

Hope this might help...

Thank you for the response. I will read through the posts you lined above and see if I can figure something out.
I honestly don't know how to access the CMD for the USG to add that line.
I did swap the DHCP DNS servers to 1.1.1.1 and 8.8.8.8 respectively for DNS 1 and DNS 2. No change.
I think it must be something in my uNraid settings that I messed up somewhere along the way years back but never found because everything else worked.

If anyone else can have a look at my post, I would greatly appreciate it. Still trying to fix this with no luck. :(

what gave you the idea that unraid runs a dns server on 127.0.0.1 ?

There is none, so nobody will answer any queries.

Delete the entry for DNS1 and move up all others, then it should work.

6 hours ago, MAM59 said:

what gave you the idea that unraid runs a dns server on 127.0.0.1 ?

There is none, so nobody will answer any queries.

Delete the entry for DNS1 and move up all others, then it should work.

I changed what you mentioned and all seems to work now. Thank you so much man, I sincerely appreciate it!
As to why it was like that, I honestly don't recall why.