| super_koza | Hi! | 20:48 |
|---|---|---|
| super_koza | I am having issues with SSH on my home server. | 20:48 |
| super_koza | I can't SSH into it using the domain name, but I can reach it with the IP address. | 20:49 |
| super_koza | On the other hand, I can access services using the domain name. | 20:49 |
| super_koza | What could be going on_ | 20:49 |
| super_koza | I am using freeDNS for dynamic DNS. | 20:51 |
| super_koza | Also Ubuntu Server 18.04. | 20:51 |
| tomreyn | super_koza: when you run "ping -c1 domainname" (replace "domainname" by your domain name), does it resolve to the same ip address you would ssh to? | 22:01 |
| super_koza | tomreyn: No, it doesn't. | 22:02 |
| tomreyn | super_koza: so that's why, you're connecting differently. | 22:02 |
| super_koza | The address that is listed in the freeDNS (afraid) is working for SSH. Domain name is working for services hosted on the server. | 22:03 |
| tomreyn | super_koza: chances are that your domain name resolves to your routers' public ip address, which is generally fine. and that you ssh to your lan ip address. is this correct? | 22:03 |
| super_koza | No. | 22:03 |
| super_koza | I will send you the addresses... | 22:03 |
| tomreyn | !pm | 22:04 |
| ubottu | Please ask your questions in the channel so that other people can help you, benefit from your questions and answers, and ensure that you're not getting bad advice. | 22:04 |
| super_koza | So it is no lan IP, but rather a public IP. | 22:05 |
| tomreyn | i will need to whitelist you to receive private messages from you, i discard them by default. i don't really need to know the addresses, you could just explain which address ranges they are from, or how you connect differently. | 22:05 |
| super_koza | Ok, I just didn't want to share them publicly. | 22:05 |
| super_koza | So, the address listed in freeDNS is something like: 33.233.232.2 | 22:06 |
| tomreyn | what probably matters here is where you are connecting from, and which ip address ranges those different domain names (the 'main' domain name and the subdomains) resolve to. | 22:06 |
| tomreyn | ok, go on. | 22:07 |
| super_koza | And the one that I get when pinging or SSHing 69.197.18.182 | 22:07 |
| super_koza | I am connecting from a remote location. | 22:07 |
| super_koza | So I am not inside the network. | 22:07 |
| super_koza | Everything used to work, until a power outage occured. I guess that is when the IP got changed, and everything got broken... | 22:08 |
| tomreyn | hmm so two different public ip addresses both connect to your ssh server? | 22:08 |
| super_koza | No... | 22:08 |
| super_koza | The first one is the actual address I think. | 22:08 |
| super_koza | The second one might be the old one, which doesn't work now. | 22:09 |
| tomreyn | 33.233.232.2 = "the first one"? | 22:09 |
| super_koza | Yes | 22:09 |
| super_koza | That is the address that I see with my DynDNS provider. | 22:09 |
| super_koza | And I can ping and ssh with it. | 22:09 |
| tomreyn | so where do you get the 69.197.18.182 address from? | 22:10 |
| super_koza | when I use the domain name, I can reach services hosted on it, like nextcloud and so on... | 22:10 |
| super_koza | but when I ping with the domain name, I get that 69.197... address. | 22:10 |
| super_koza | No idea how. | 22:10 |
| super_koza | Maybe I could try clearing the DNS cache on my client PC. | 22:11 |
| tomreyn | so the dns for this domain name, is it managed by your freedns service, or is it manually updated by you? | 22:11 |
| super_koza | It is updated with a cron job | 22:12 |
| tomreyn | okay, i give up, i'll whitelist you. | 22:12 |
| super_koza | the current IP is there | 22:13 |
| super_koza | I have to run now | 22:13 |
| super_koza | is it OK if I write you later | 22:13 |
| super_koza | ? | 22:13 |
| tomreyn | i'll probably not be around then, maybe yomeone else will be | 22:13 |
| tomreyn | but you can try. | 22:13 |
| super_koza | Have you got my messages? | 22:14 |
| tomreyn | no, they went nowhere. but you can PM me now. | 22:14 |
| tomreyn | got them now. | 22:16 |
| leftyfb | um | 22:28 |
| leftyfb | super_koza: we already went through all this | 22:28 |
| leftyfb | super_koza: that domain does not point to the correct ip. Plain and simple. contact the dyndns/domain provider for support. | 22:30 |
| leftyfb | super_koza: cloud.<your.domain> does. But the top domain does not. | 22:32 |
| leftyfb | That is why your nextcloud works | 22:33 |
| leftyfb | super_koza: something at the provider forwards it | 22:33 |
| tomreyn | right | 22:36 |
| leftyfb | super_koza: If you had contacted your provider, they would have figured this out for you and probably even resolved it. It is in no way an issue with or related to Ubuntu. | 22:36 |
| leftyfb | an hour ago | 22:37 |
| tomreyn | "You're going to help us, Mr. Anderson. Whether you want to or not." | 22:41 |
| leftyfb | "Because I choose to" | 22:42 |
| tomreyn | Yes, freedns.afraid.org is a service run by Joshua Anderson, who chose to provide an awesome free service and fighting against the (DDoS) windmills of the Internet and does so for 18 years now. | 22:44 |
| tomreyn | oops, OT | 22:44 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!