Hey guys hit bit of an issue. I been trying to get some scripts up and running for LFTP to automatically download from my seedbox to my unRaid server directly.

It looks like I may have broken something and I don't know what. Via unRaid's terminal I can no longer SSH into my seedbox. When I type in

ssh box.hostname.eu

it hangs for a few seconds then returns

"ssh: Could not resolve hostname box.hostname.eu: Name or service not known"

It was working just last night. I tried to SSH into another box via unRaid's Terminal and I was able to. Any idea how to fix this? I can still SSH into the seedbox via PuTTY with no issues I just can't do it via unRaids Terminal anymore, and then as a result I can't even LFTP now either. I deleted all scripts but this had no effect.

What is the output of:
nslookup box.hostname.eu 

and
traceroute box.hostname.eu

I have a feeling whatever local DNS unraid is using is unable to resolve that hostname.

40 minutes ago, Xaero said:

What is the output of:
nslookup box.hostname.eu 

and
traceroute box.hostname.eu

I have a feeling whatever local DNS unraid is using is unable to resolve that hostname.

This is what I get for nslookup

 

-bash: nslookup: command not found

traceroute works though

 

5  bundle-ether20.chw-core10.sydney.telstra.net (203.50.11.180)  26.168 ms  26.232 ms  26.166 ms
 6  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  26.514 ms  19.699 ms bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  23.270 ms
 7  bundle-ether2.oxf-gw10.sydney.telstra.net (203.50.6.94)  27.066 ms bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  29.669 ms  29.645 ms
 8  bundle-ether1.sydo-core04.sydney.reach.com (203.50.13.94)  26.463 ms i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  162.834 ms bundle-ether1.sydo-core04.sydney.reach.com (203.50.13.94)  28.322 ms
 9  i-92.eqnx03.telstraglobal.net (202.84.247.17)  164.917 ms i-10604.1wlt-core02.telstraglobal.net (202.84.141.225)  202.546 ms  201.176 ms
10  i-0-6-0-1.paix-core02.telstraglobal.net (202.84.143.198)  210.219 ms ae30-472.cr6-sjc1.ip4.gtt.net (173.205.49.221)  164.411 ms i-0-6-0-1.paix-core02.telstraglobal.net (202.84.143.198)  210.184 ms
11  ae12.cr2-ams2.ip4.gtt.net (213.254.231.110)  341.839 ms  341.849 ms  341.895 ms
12  ip4.gtt.net (46.33.78.21)  336.616 ms 134.159.61.98 (134.159.61.98)  201.853 ms  201.672 ms
13  ae17.cr2-ams2.ip4.gtt.net (89.149.143.178)  334.568 ms  339.321 ms  339.296 ms
14  ip4.gtt.net (46.33.78.21)  343.287 ms ip4.gtt.net (46.33.78.17)  341.707 ms  345.860 ms
15  * box.seedbox.eu (37.48.xx.xx)  340.330 ms *

Ha! Funny it now works and I can SSH into the box from Terminal?

 

I left it alone for a while went out to grab a coffee and came back and it worked

Edited January 11, 20206 yr by z0ki

Interesting; if traceroute works that would imply that dns resolution is working which means ssh <hostname> should work.

On that note; does ssh 37.48.xx.xx work?

If so; 
ssh -vvv box.seedbox.eu may provide useful information.

EDIT: 
Also I feel like nslookup should be in the default package list? Am I wrong on this?

Edited January 11, 20206 yr by Xaero

9 minutes ago, Xaero said:

Interesting; if traceroute works that would imply that dns resolution is working which means ssh <hostname> should work.

On that note; does ssh 37.48.xx.xx work?

If so; 
ssh -vvv box.seedbox.eu may provide useful information.

EDIT: 
Also I feel like nslookup should be in the default package list? Am I wrong on this?

I couldn't tell you if it is part of the list or not. I did try a nslookup earlier this morning but it resulted in the same 'command not found' but thought it was odd it didn't work as I've seen that command being mentioned a fair bit on here.

 

Odd that it's just starting working again though lol. I got a pretty straight forward setup so not much that could go wrong i initailly thought maybe one of the scripts I was testing was maybe now blocking ssh to that seedbox but seems that wasn't the case. But whilst ssh was not working I couldn't use LFTP either it threw the same (host not found) kind of error. So maybe it was a DNS lookup issue? Who knows. I'm still an utter amateur at anything 'command' based so take what I say with a handful of salt haha

Unraid doesn't have any of the dns tools installed.

and since it wasn't working for a short while, I suspect it was just a DNS lookup issue.

Another way to double check is to just

ping hostname -c1

and see if ping can resolve the hostname correctly.

3 minutes ago, ken-ji said:

Unraid doesn't have any of the dns tools installed.

and since it wasn't working for a short while, I suspect it was just a DNS lookup issue.

Another way to double check is to just

ping hostname -c1

and see if ping can resolve the hostname correctly.

 

That command works :)

 

I'll keep that one in mind for next time then! I just assumed something was wrong with my unRaid as it was working on my Windows machine with PuTTY. Was worried I wrecked something haha