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.

Hostname/DNS Issues -- External IPs resolve as 127.0.0.1

Featured Replies

Excellent identity crisis example. :)

 

The source is kind of a mess. Dangerously unclear intent, as if different people kept finding it and adding things, fitting it to their own purpose. But that doesn't happen.

  • Replies 52
  • Views 20k
  • Created
  • Last Reply

After a fresh restart, I ran hostname smtp.gmail.com -i , and it still loops back to 127.0.0.1.

 

I don't think hostname is really the best tool to use here. unRAID should really include dig or nslookup at a minimum.

 

DNS Resolution appears to be working in unRAID (demonstrated by the fact that the NTP daemon etc can resolve domains), so why SOCAT isn't resolving DNS, I'm not sure. I think easiest way to sort this is to move the unraid_notify script to send via SSMTP.

 

I should say that unRAID needs a search domain field in DNS settings as well.

 

"hostname" is definitely a bit weird...

 

+!1 on

unRAID should really include dig or nslookup at a minimum
.

I think easiest way to sort this is to move the unraid_notify script to send via SSMTP.
Moving to SSMTP would be a pretty good idea, as we all use that for health status/UPS/Preclear, etc. emails.

 

 

I should say that unRAID needs a search domain field in DNS settings as well.
BIG +1 on this, Tom should definitley add this.

After a fresh restart, I ran hostname smtp.gmail.com -i , and it still loops back to 127.0.0.1.

 

I don't think hostname is really the best tool to use here. unRAID should really include dig or nslookup at a minimum.

 

DNS Resolution appears to be working in unRAID (demonstrated by the fact that the NTP daemon etc can resolve domains), so why SOCAT isn't resolving DNS, I'm not sure. I think easiest way to sort this is to move the unraid_notify script to send via SSMTP.

 

I should say that unRAID needs a search domain field in DNS settings as well.

I always use "net lookup"  It always returns the external IP if a DNS server and gateway are defined.

 

root@Tower2:~# net lookup smtp.gmail.com

74.125.113.109

 

I've never use the -i option to hostname, I only ever remember it being used to return the name of the current host.

 

 

"hostname" is definitely a bit weird...

 

+!1 on

unRAID should really include dig or nslookup at a minimum
.

I think easiest way to sort this is to move the unraid_notify script to send via SSMTP.
Moving to SSMTP would be a pretty good idea, as we all use that for health status/UPS/Preclear, etc. emails.

 

 

I should say that unRAID needs a search domain field in DNS settings as well.
BIG +1 on this, Tom should definitley add this.

Archived

This topic is now archived and is closed to further replies.

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.