SSH-accessible public ADOM server online (experimental)

[btt]

That's very strange:

C:\Program Files (x86)\Console2>nslookup ancardia.us.to 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

*** google-public-dns-a.google.com can't find ancardia.us.to: Non-existent domain

C:\Program Files (x86)\Console2>nslookup ancardia.us.to 208.67.222.222
Server:  resolver1.opendns.com
Address:  208.67.222.222

Non-authoritative answer:
Name:    ancardia.us.to
Address:  198.101.219.241


C:\Program Files (x86)\Console2>nslookup ancardia.us.to 75.75.76.76
Server:  UnKnown
Address:  75.75.76.76

*** UnKnown can't find ancardia.us.to: Query refused

C:\Program Files (x86)\Console2>nslookup ancardia.us.to ns3.afraid.org
Server:  UnKnown
Address:  72.20.15.62

Name:    ancardia.us.to
Address:  198.101.219.241

Obviously we can ignore 75.75.76.76 (presumably ComCast) since it doesn't want to talk to me, but Google is telling me it doesn't exist, as is my ISPs DNS. Now I can't reach the us.to page I was looking at earlier either. It must be some local issue (I'm in the UK)...

As I say, it was working fine early this morning, then suddenly stopped around lunchtime.

[zarkone]

That's very strange:

C:\Program Files (x86)\Console2>nslookup ancardia.us.to 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

*** google-public-dns-a.google.com can't find ancardia.us.to: Non-existent domain

C:\Program Files (x86)\Console2>nslookup ancardia.us.to 208.67.222.222
Server:  resolver1.opendns.com
Address:  208.67.222.222

Non-authoritative answer:
Name:    ancardia.us.to
Address:  198.101.219.241


C:\Program Files (x86)\Console2>nslookup ancardia.us.to 75.75.76.76
Server:  UnKnown
Address:  75.75.76.76

*** UnKnown can't find ancardia.us.to: Query refused

C:\Program Files (x86)\Console2>nslookup ancardia.us.to ns3.afraid.org
Server:  UnKnown
Address:  72.20.15.62

Name:    ancardia.us.to
Address:  198.101.219.241

Obviously we can ignore 75.75.76.76 (presumably ComCast) since it doesn't want to talk to me, but Google is telling me it doesn't exist, as is my ISPs DNS. Now I can't reach the us.to page I was looking at earlier either. It must be some local issue (I'm in the UK)...

As I say, it was working fine early this morning, then suddenly stopped around lunchtime.

Approve, from russia domain http://ancardia.us.to/ unresolved. BTW, when i

$ ssh 198.101.219.241

what username\pass i should use? i visit this server first time, i didn't find any adom servers but want to watch how other people play, i'm newbye..

[Alucard]

I don't know what's going on with DNS, but if ancardia.us.to doesn't work for you, try ancardia.dyndns.org

what username\pass i should use? i visit this server first time, i didn't find any adom servers but want to watch how other people play, i'm newbye..

Instructions are at http://ancardia.dyndns.org/#connect

[zarkone]

thanks, very helpfull! enjoing watching =)

[Grey]

Before this post there were 404 posts in this thread. Very appropriate... This thread has now been unstuck, with the following thread from Alucard now promoted to sticky status as it has more up to date info:

http://www.adom.de/forums/showthread...-accessible%29