Hi,
I just read the FAQ. However it appears that shell.cl.net is running a normal web server on port 80 and nothing on port 443. I expected sshd on both, according to the FAQ.
Regards, Jörg Höhle.
Hi Andreas,
have you discontinued the shell service?
Thanks, Erik.
On 11/6/06, Hoehle, Joerg-Cyril Joerg-Cyril.Hoehle@t-systems.com wrote:
Hi,
I just read the FAQ. However it appears that shell.cl.net is running a normal web server on port 80 and nothing on port 443. I expected sshd on both, according to the FAQ.
Regards, Jörg Höhle. _______________________________________________ admin mailing list admin@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/admin
Erik Enge wrote:
Hi Andreas,
Hi!
have you discontinued the shell service?
No, I haven't. But:
$ host shell.common-lisp.net shell.common-lisp.net A 80.68.86.115
That's cl.net's ip address, isn't it?
I think just correcting the dns record to point to 86.59.21.101 should make everything work again.
Cheers,
On 11/7/06, Andreas Fuchs asf@boinkor.net wrote:
I think just correcting the dns record to point to 86.59.21.101 should make everything work again.
Oops, sorry. Fixed! Should make it's way around to a DNS server near you within a few hours.
Thanks, Erik.
Erik Enge wrote:
I think just correcting the dns record to point to
86.59.21.101 should
make everything work again.
Oops, sorry. Fixed! Should make it's way around to a DNS server near you within a few hours.
Hmm, that was 3 days ago on Nov. the 7th, and now it (shell[s].common-lisp.net) still says 80.68...
nslookup reports Got answer (138 bytes): HEADER: opcode = QUERY, id = 5, rcode = NOERROR header flags: response, want recursion, recursion avail. questions = 1, answers = 1, authority records = 2, additional = 2
QUESTIONS: shell.common-lisp.net, type = ANY, class = IN ANSWERS: -> shell.common-lisp.net type = A, class = IN, dlen = 4 internet address = 80.68.86.115 ttl = 14207 (3 hours 56 mins 47 secs) AUTHORITY RECORDS: -> common-lisp.net type = NS, class = IN, dlen = 20 nameserver = dns10.register.com ttl = 14207 (3 hours 56 mins 47 secs) -> common-lisp.net type = NS, class = IN, dlen = 7 nameserver = dns9.register.com ttl = 14207 (3 hours 56 mins 47 secs) ADDITIONAL RECORDS: -> dns9.register.com type = A, class = IN, dlen = 4 internet address = 216.21.234.75 ttl = 156018 (1 day 19 hours 20 mins 18 secs) -> dns10.register.com type = A, class = IN, dlen = 4 internet address = 216.21.226.75 ttl = 164242 (1 day 21 hours 37 mins 22 secs)
------------ Non-authoritative answer: shell.common-lisp.net type = A, class = IN, dlen = 4 internet address = 80.68.86.115 ttl = 14207 (3 hours 56 mins 47 secs) Authoritative answers can be found from: common-lisp.net type = NS, class = IN, dlen = 20 nameserver = dns10.register.com ttl = 14207 (3 hours 56 mins 47 secs) common-lisp.net type = NS, class = IN, dlen = 7 nameserver = dns9.register.com ttl = 14207 (3 hours 56 mins 47 secs) dns9.register.com type = A, class = IN, dlen = 4 internet address = 216.21.234.75 ttl = 156018 (1 day 19 hours 20 mins 18 secs) dns10.register.com type = A, class = IN, dlen = 4 internet address = 216.21.226.75 ttl = 164242 (1 day 21 hours 37 mins 22 secs)
On 11/10/06, Hoehle, Joerg-Cyril Joerg-Cyril.Hoehle@t-systems.com wrote:
Hmm, that was 3 days ago on Nov. the 7th, and now it (shell[s].common-lisp.net) still says 80.68...
Weird, the register.com interface shows no sign of my adding a CNAME for shell.common-lisp.net pointing to that IP. I've just added it again. Hopefully it'll "stick" this time. :-(
Let me know if it doesn't and I'll open a support ticket.
Erik.
-
Andreas Fuchs -
Erik Enge -
Hoehle, Joerg-Cyril