Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Can nslookup but can't curl FQDN hosted locally

Featured Replies

root@myUnraidAccount:~# nslookup app.myhostname.com
Server:         192.168.1.123
Address:        192.168.1.123#53

Non-authoritative answer:
app.myhostname.com   canonical name = myhostname2.com.
Name:   myhostname2.com
Address: 167.123.12.123
 
root@myUnraidAccount:~# curl -v https://app.myhostname.com -4
*   Trying 167.123.12.123:443...
* connect to 167.123.12.123 port 443 failed: Connection refused
* Failed to connect to app.myhostname.com port 443 after 2040 ms: Couldn't connect to server
* Closing connection
curl: (7) Failed to connect to app.myhostname.com port 443 after 2040 ms: Couldn't connect to server
root@myUnraidAccount:~# curl -v https://app.myhostname.com -6
* Could not resolve host: app.myhostname.com
* Closing connection
curl: (6) Could not resolve host: app.myhostname.com
root@myUnraidAccount:~# traceroute https://app.myhostname.com
https://app.myhostname.com: Name or service not known
Cannot handle "host" cmdline arg `https://app.myhostname.com' on position 1 (argc 1)
root@myUnraidAccount:~# traceroute app.myhostname.com
traceroute to app.myhostname.com (167.123.12.123), 30 hops max, 60 byte packets
 1  167.123.12.123 (167.123.12.123)  37.629 ms  37.624 ms  37.620 ms

 

My `/etc/resolv.conf`

 

root@myUnraidAccount:~# cat /etc/resolv.conf
# Generated by dhcpcd from br0.dhcp
nameserver 192.168.1.124
nameserver 192.168.1.123
# Generated by rc.inet1

 

My `/etc/hosts`

 

root@myUnraidAccount:~# cat /etc/hosts
# Generated
127.0.0.1 myUnraidAccount localhost
54.149.176.35     keys.lime-technology.com

 

When I tried to `curl` in my UnRaid terminal `app.myhostname.com`, it's failed, but `nslookup` work.

 

Any idea what's wrong with my `resolv.conf` or `hosts`? Both of them are default generated, I don't touch them.

Solved by shawnngtq

  • Author

Attached diagnostic

 

Edited by shawnngtq

  • Author

This issue happen only on the UnRaid terminal and docker containers.

 

I can curl from my VM.

 

I suspect it means issue is specific to UnRaid + docker network interface

  • 4 weeks later...
  • Author
  • Solution

I configured WireGuard server-to-server tunnel, that causes this issue.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.