Banned myself from my own server, or something with my DNS?

Question

I can't seem to ssh or even browse my site ( medero.org ) even though it's resolving to my server's ip, but other people can.

I was SFTPing some files earlier, but nothing out of the ordinary.

How is it possible that I can't ssh or ping but other people can? I hope I didn't blacklist myself somehow.

The distro is debian, fairly new ( this year ), I don't remember explicitly setting up a blacklist application.

me@dunross:~$ ssh user@72.44.90.147
ssh: connect to host 72.44.90.147 port 22: Connection timed out

score 1 · Answer 1 · answered Jul 08 '10 at 18:57

1

There's some other issue. A firewall or blacklist rule on their side would result in "connection refused", not a timeout.

Check from another computer on your local network, and if possible from your computer on another network.

answered Jul 08 '10 at 18:57

Daenyth

243
1
7

3

Connections may timeout when firewalled. This is the case, for instance, with iptables if the rule uses the target DROP instead of REJECT. – b0fh Jul 08 '10 at 19:08
Good catch, I hadn't thought of that. – Daenyth Jul 08 '10 at 20:19

score 1 · Answer 2 · answered Jul 08 '10 at 19:31

1

Add iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

Sounds like the port it blocked on the Debian box.

answered Jul 08 '10 at 19:31

colealtdelete

6,009
1
29
34

score 1 · Answer 3 · answered Jul 08 '10 at 20:37

There are daemons, like fail2ban, that auto-ban IPs that get to many auth errors. They eventually time out the ban, so if you have one of these you could just wait.

Have you tried pinging another IP at the same site. Using whois you can see the IP block of that site and ping another machine. I was able to ping your IP (72.44.90.147) and its neighbor 72.44.90.148 fine. If you can ping other machines at that site that would eliminate a general networking problem.

Banned myself from my own server, or something with my DNS?

3 Answers3