Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

news.eternal.september.org does not work for the last 8 hours

250 views
Skip to first unread message

Carla Schneider

unread,
Jul 1, 2022, 2:05:19 AM7/1/22
to
Connect fails.

reader.eternal.september does work.

Ray Banana

unread,
Jul 1, 2022, 2:37:42 AM7/1/22
to
On 10531 September 1993, Carla Schneider wrote:

> Connect fails.
> reader.eternal.september does work.

news.eternal-september.org and reader.eternal-september.org are aliases
for the same server and have been since June 26.

The old server reader02.eternal-september.org was shut down yesterday.
Please check your server configuration for news.eternal-september.org.
Do you use the IP address or the server name
reader02.eternal-september.org?

--
Too many ingredients in the soup, no room for a spoon
http://www.eternal-september.org

ERSHC

unread,
Jul 1, 2022, 3:10:23 AM7/1/22
to
On Fri, 01 Jul 2022 08:37:41 +0200, Ray Banana <ray...@raybanana.net> wrote:
> On 10531 September 1993, Carla Schneider wrote:
>
>> Connect fails.
>> reader.eternal.september does work.
>
> news.eternal-september.org and reader.eternal-september.org are aliases
> for the same server and have been since June 26.
>
> The old server reader02.eternal-september.org was shut down yesterday.
> Please check your server configuration for news.eternal-september.org.
> Do you use the IP address or the server name
> reader02.eternal-september.org?
>

Just another data point: news.eternal-september.org (by name, not IP)
stopped working for me, but reader80.eternal-september.org is fine.

Marco Moock

unread,
Jul 2, 2022, 2:57:00 AM7/2/22
to
Am Freitag, 01. Juli 2022, um 07:10:22 Uhr schrieb ERSHC:

> Just another data point: news.eternal-september.org (by name, not IP)
> stopped working for me, but reader80.eternal-september.org is fine.

For me it works, do you really use the domain name and not an IP
address?
Have you cleared your DNS cache?

ERSHC

unread,
Jul 2, 2022, 3:38:20 PM7/2/22
to
Yes, by name not IP:

Connecting to host news.eternal-september.org ...
Unable to make connection. Giving up.

Run-Time Error
slrn fatal error:
Failed to initialize server.

Maybe it is the DNS:
ershc@ershcBox:~$ ping news.eternal-september.org
PING news.eternal-september.org (144.76.35.198) 56(84) bytes of data.
64 bytes from news.eternal-september.org (144.76.35.198): icmp_seq=1 ttl=50 time=105 ms

but
ershc@ershcBox:~$ ping reader80.eternal-september.org
PING reader01.eternal-september.org (88.198.57.247) 56(84) bytes of data.
64 bytes from reader01.eternal-september.org (88.198.57.247): icmp_seq=1 ttl=50 time=108 ms

And flushing DNS cache doesn't change it:
ershc@ershcBox:~$ sudo killall -HUP dnsmasq
ershc@ershcBox:~$ ping news.eternal-september.org
PING news.eternal-september.org (144.76.35.198) 56(84) bytes of data.
64 bytes from news.eternal-september.org (144.76.35.198): icmp_seq=1 ttl=50 time=107 ms

I suppose it could be my provider not updating their DNS?

Thanks!

Bit Twister

unread,
Jul 2, 2022, 3:46:37 PM7/2/22
to
On Sat, 2 Jul 2022 19:38:19 -0000 (UTC), ERSHC wrote:
> On Sat, 2 Jul 2022 08:56:58 +0200, Marco Moock <mo...@posteo.de> wrote:
>> Am Freitag, 01. Juli 2022, um 07:10:22 Uhr schrieb ERSHC:
>>
>>> Just another data point: news.eternal-september.org (by name, not IP)
>>> stopped working for me, but reader80.eternal-september.org is fine.
>>
>> For me it works, do you really use the domain name and not an IP
>> address?
>> Have you cleared your DNS cache?
>>
>
> Yes, by name not IP:
>
> Connecting to host news.eternal-september.org ...
> Unable to make connection. Giving up.
>
> Run-Time Error
> slrn fatal error:
> Failed to initialize server.
>
> Maybe it is the DNS:
> ershc@ershcBox:~$ ping news.eternal-september.org
> PING news.eternal-september.org (144.76.35.198) 56(84) bytes of data.
> 64 bytes from news.eternal-september.org (144.76.35.198): icmp_seq=1 ttl=50 time=105 ms
>
> but
> ershc@ershcBox:~$ ping reader80.eternal-september.org
> PING reader01.eternal-september.org (88.198.57.247) 56(84) bytes of data.
> 64 bytes from reader01.eternal-september.org (88.198.57.247): icmp_seq=1 ttl=50 time=108 ms
--- reader01.eternal-september.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 128.230/128.230/128.230/0.000 ms

> And flushing DNS cache doesn't change it:
> ershc@ershcBox:~$ sudo killall -HUP dnsmasq
> ershc@ershcBox:~$ ping news.eternal-september.org
> PING news.eternal-september.org (144.76.35.198) 56(84) bytes of data.
> 64 bytes from news.eternal-september.org (144.76.35.198): icmp_seq=1 ttl=50 time=107 ms


$ ping -4c1 news.eternal-september.org
PING reader01.eternal-september.org (88.198.57.247) 56(84) bytes of data.
64 bytes from reader01.eternal-september.org (88.198.57.247): icmp_seq=1 ttl=53 time=128 ms

Using named on Mageia Linux OS as my dns server.

> I suppose it could be my provider not updating their DNS?

Well, change dns server to a public dns server and see what happens.

http://www.topbits.com/public-dns-servers.html
http://code.google.com/speed/public-dns/docs/security.html
http://csrc.nist.gov/publications/nistpubs/800-81/SP800-81.pdf
http://www.opennic.unrated.net/public_servers.html

Marco Moock

unread,
Jul 2, 2022, 4:06:34 PM7/2/22
to
Am Samstag, 02. Juli 2022, um 19:38:19 Uhr schrieb ERSHC:

> I suppose it could be my provider not updating their DNS?

Maybe the cache time of the authoritative DNS server from ES was the
problem. I don't know the last value of their record, but this can be
more than 1 day.
Maybe try another DNS recursor (e.g. your own BIND).

Lewis

unread,
Jul 2, 2022, 6:22:29 PM7/2/22
to
In message <t9q6rb$2mn0a$1...@dont-email.me> ERSHC <ersh...@invalid.invalid> wrote:
> On Sat, 2 Jul 2022 08:56:58 +0200, Marco Moock <mo...@posteo.de> wrote:
>> Am Freitag, 01. Juli 2022, um 07:10:22 Uhr schrieb ERSHC:
>>
>>> Just another data point: news.eternal-september.org (by name, not IP)
>>> stopped working for me, but reader80.eternal-september.org is fine.
>>
>> For me it works, do you really use the domain name and not an IP
>> address?
>> Have you cleared your DNS cache?
>>

> Yes, by name not IP:

And you are correct to do so. You should never hardcode an IP if you can
at all avoid it.

> Connecting to host news.eternal-september.org ...
> Unable to make connection. Giving up.

> Run-Time Error
> slrn fatal error:
> Failed to initialize server.

Well, that's not normal

> Maybe it is the DNS:
> ershc@ershcBox:~$ ping news.eternal-september.org
> PING news.eternal-september.org (144.76.35.198) 56(84) bytes of data.
> 64 bytes from news.eternal-september.org (144.76.35.198): icmp_seq=1 ttl=50 time=105 ms

That's definitely not right.

> but
> ershc@ershcBox:~$ ping reader80.eternal-september.org
> PING reader01.eternal-september.org (88.198.57.247) 56(84) bytes of data.
> 64 bytes from reader01.eternal-september.org (88.198.57.247): icmp_seq=1 ttl=50 time=108 ms

$ dig news.eternal-september.org +short
reader01.eternal-september.org.
88.198.57.247

> And flushing DNS cache doesn't change it:

Did you do something in your /etc/hosts?

grep -r 144.76.35.198 /etc/

> ershc@ershcBox:~$ sudo killall -HUP dnsmasq
> ershc@ershcBox:~$ ping news.eternal-september.org
> PING news.eternal-september.org (144.76.35.198) 56(84) bytes of data.
> 64 bytes from news.eternal-september.org (144.76.35.198): icmp_seq=1 ttl=50 time=107 ms

> I suppose it could be my provider not updating their DNS?

Try using a more reliable DNS server? 1.1.1.1 or 9.9.9.9 are my go to
servers when seeing if something is wonky.

# dig news.eternal-september.org @1.1.1.1 +short
reader01.eternal-september.org.
88.198.57.247
# dig news.eternal-september.org @9.9.9.9 +short
reader01.eternal-september.org.
88.198.57.247
# dig news.eternal-september.org @8.8.8.8 +short
reader01.eternal-september.org.
88.198.57.247

--
"Whose motorcycle is this?" "It's chopper, baby." "Whose chopper is
this?" "It's Zed's." "Who's Zed?" "Zed' dead, baby. Zed's dead."

ERSHC

unread,
Jul 2, 2022, 10:13:36 PM7/2/22
to
On Sat, 2 Jul 2022 22:22:28 -0000 (UTC), Lewis <g.k...@gmail.dontemailme.com> wrote:
> In message <t9q6rb$2mn0a$1...@dont-email.me> ERSHC <ersh...@invalid.invalid> wrote:
<delitia>
>> Maybe it is the DNS:
>> ershc@ershcBox:~$ ping news.eternal-september.org
>> PING news.eternal-september.org (144.76.35.198) 56(84) bytes of data.
>> 64 bytes from news.eternal-september.org (144.76.35.198): icmp_seq=1 ttl=50 time=105 ms
>
> That's definitely not right.
>
<deletia>
>
>> And flushing DNS cache doesn't change it:
>
> Did you do something in your /etc/hosts?
>

Thank you! I have no idea WHY I would have done that (was there a DNS
problem 10 years ago with this a "temporary" fix?) but indeed, there
was a hosts entry. I am a fool.
0 new messages