Timeline for Cannot ssh anymore via no-ip hostname, works with wan ip, nslookup gives nxdomain
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 4, 2023 at 8:59 | history | edited | florianbo | CC BY-SA 4.0 |
added 316 characters in body
|
| Mar 3, 2023 at 17:55 | vote | accept | florianbo | ||
| Mar 3, 2023 at 16:22 | history | edited | florianbo | CC BY-SA 4.0 |
added 254 characters in body
|
| Mar 3, 2023 at 15:58 | history | edited | florianbo | CC BY-SA 4.0 |
deleted 157 characters in body
|
| Mar 3, 2023 at 15:16 | answer | added | npochet | timeline score: 0 | |
| Mar 3, 2023 at 13:13 | comment | added | florianbo | Thanks again! I edited my post with the additional infos. I tried to ssh from 3 different machines (pop!os, mac and an android phone, which all used to work before) and ended with the same results. I did not setup any particular dns in the machines. And the only modification I made since last week is a few regular updates. | |
| Mar 3, 2023 at 13:06 | history | edited | florianbo | CC BY-SA 4.0 |
added 915 characters in body
|
| Mar 3, 2023 at 12:57 | history | edited | florianbo | CC BY-SA 4.0 |
added 915 characters in body
|
| Mar 3, 2023 at 12:49 | comment | added | gepa | OK, this means ddns is fine, and the issue is in your local system from which you are trying to ssh. What system are you running, and can you share any dns configuration you have, or something that you changed a week ago, when it stopped working. Also, instead of answering in the comments, it is better to edit your question with the additional information. That helps everybody understand your issue better, and possibly find a way to help. | |
| Mar 3, 2023 at 12:39 | comment | added | florianbo |
Thanks for your answer. Noip shows that my hostname is indeed active, here is a screenshot of the entry: link When I check using nslookup.io, I see that my wan ip is returned. And I receive the following with dig @wan.ip mydoamin.ddns.net: (1 server found) global options: +cmd Got answer: ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48655 flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 OPT PSEUDOSECTION: EDNS: version: 0, flags:; udp: 1232 COOKIE: f4d61592bacb5e1f010000006401e94ef8b8411a85020221 (good)
|
|
| Mar 3, 2023 at 11:39 | comment | added | gepa |
Since you say connecting directly by IP address works, it is some problem with the DNS resolution. Either it is your local dns resolver (do you get any results if you check directly at a public resolver, e.g. what does dig @8.8.8.8 mydomain.ddns.net give you, or try some online resolver like nslookup.io . If these also give you NXDOMAIN, it means ddns did not really update the record. you write "everything seems fine", but can you post e.g. a screenshot of my.noip.com/dynamic-dns with your entry? Does it say "Active" under the entry?
|
|
| S Mar 3, 2023 at 11:23 | review | First questions | |||
| Mar 3, 2023 at 11:41 | |||||
| S Mar 3, 2023 at 11:23 | history | asked | florianbo | CC BY-SA 4.0 |