From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 24468 invoked from network); 11 Jan 2023 18:16:20 -0000
Received: from mx1.math.uh.edu (129.7.128.32)
  by inbox.vuxu.org with ESMTPUTF8; 11 Jan 2023 18:16:20 -0000
Received: from lists1.math.uh.edu ([129.7.128.208])
	by mx1.math.uh.edu with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <ding-owner+M39263=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1pFfe5-006yJG-90
	for ml@inbox.vuxu.org; Wed, 11 Jan 2023 12:16:17 -0600
Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu)
	by lists1.math.uh.edu with smtp (Exim 4.96)
	(envelope-from <ding-owner+M39263=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1pFfe4-005Kt2-2z
	for ml@inbox.vuxu.org;
	Wed, 11 Jan 2023 12:16:17 -0600
Received: from mx1.math.uh.edu ([129.7.128.32])
	by lists1.math.uh.edu with esmtp (Exim 4.96)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1pDncc-005696-1Q
	for ding@lists.math.uh.edu;
	Fri, 06 Jan 2023 08:23:02 -0600
Received: from quimby.gnus.org ([95.216.78.240])
	by mx1.math.uh.edu with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1pDncZ-003KNX-Jd
	for ding@lists.math.uh.edu; Fri, 06 Jan 2023 08:23:02 -0600
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org;
	 s=20200322; h=Content-Type:Mime-Version:Message-ID:Date:Subject:From:To:
	Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description:
	Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:
	In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
	List-Post:List-Owner:List-Archive;
	bh=KSPdc5FDx+XsjzOWWOEQug2z1XLN2xb+wqwlCa6zLpk=; b=hphgF/j1FAtmP0dVMkHc4nva/u
	srdpL5LlTMlzphkz+aPdPEsbZ26+p/ZaTKmxva0npJ7XqGV+ywwKRkGoaZ0KxFtGUnu3NzVzSIFVo
	w4T1qz9HHZ7OfXIr3dG22wYbxyzUHobw4fJu+7qAd60RCQmTl5lqFxwO1Xggy1WLJWCM=;
Received: from ciao.gmane.io ([116.202.254.214])
	by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1pDncN-0007TV-Ik
	for ding@gnus.org; Fri, 06 Jan 2023 15:22:52 +0100
Received: from list by ciao.gmane.io with local (Exim 4.92)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1pDncL-0009qN-Qa
	for ding@gnus.org; Fri, 06 Jan 2023 15:22:45 +0100
X-Injected-Via-Gmane: http://gmane.org/
Mail-Followup-To: ding@gnus.org
To: ding@gnus.org
From: Steinar Bang <sb@dod.no>
Subject: Gnus refuses to connect after suspend and resume in different network, but Gnus in fresh emacs works
Date: Fri, 06 Jan 2023 15:22:40 +0100
Organization: Probably a good idea
Message-ID: <87r0w7agjz.fsf@dod.no>
Mime-Version: 1.0
Content-Type: text/plain
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Cancel-Lock: sha1:V97quHfhn9s4VAwcmpeXJIWWi/k=
Mail-Copies-To: never
List-ID: <ding.gnus.org>
Precedence: bulk

Platform: amd64, debian 11.6 "bullseye"
          GNU Emacs 27.1,
          Gnus v5.13 (native gnus of emas 27.1)

I started the emacs process at home and ran Gnus it in for several days.

Yesterday I unplugged gnus at home, and suspended the laptop.

Today I resumed the laptop in a different LAN and tried to plug in the
unplugged gnus.

But gnus was unable to connect.

So I stopped gnus and started gnus in the old emacs process, but gnus
was still unable to connect.

But gnus started from a fresh emacs process worked fine.

Is there a way to figure out what's gone wrong with the old emacs
process?  I suspect a cached DNS server?  Is there a way to find out if
that is the case?

Has anyone else observed this behaviour?

Does anyone know how to fix this (other than starting a new emacs)?

Thanks!