From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Persistent failure to lookup hostname Date: Tue, 04 Oct 2022 09:24:36 -0400 Message-ID: References: <83mtacw073.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10349"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 04 16:22:00 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ofio4-0002TX-87 for ged-emacs-devel@m.gmane-mx.org; Tue, 04 Oct 2022 16:22:00 +0200 Original-Received: from localhost ([::1]:33522 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ofio3-0007UA-2w for ged-emacs-devel@m.gmane-mx.org; Tue, 04 Oct 2022 10:21:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53294) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofhuc-0006nN-RF for emacs-devel@gnu.org; Tue, 04 Oct 2022 09:24:43 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:27523) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofhua-0002em-Cd; Tue, 04 Oct 2022 09:24:41 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id D4AFD44318C; Tue, 4 Oct 2022 09:24:38 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 7859B44318A; Tue, 4 Oct 2022 09:24:37 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1664889877; bh=evOekmD9t+KakVKhCM5tUcNv82c9rL3bsZ88sELtm4U=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=VMy+MQaVWRE0fSRqJugC5Hvtknt/hwrCIhFOyfyDttJoG+mYiyixAIBOSF4yvWdXO 5zizoYi64J2Bg3oj26z95t5aOQG8ASch03BGKSP+M0sYSKzvhEwSpaFwFISAuZenW1 w4kcxpRFZhg38IrYqdq1ndvyKOIv1P6QoJcACF9Rf5ROYFy8JsCRTT0rP008aXHNQz dKR7lpcwngEO7BZON67uGR4xwFwYQL0x/3379pKnzWk5dncN7LJTQ7CPpcIjL5zM11 EDT22DcG29pO6byxMg07BYerzLvfjzrI2lyIZRXhAHsn18fBkx9ftlAAhNVNpBrvIm /V+fi8XguP+bQ== Original-Received: from pastel (65-110-220-202.cpe.pppoe.ca [65.110.220.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 4DE5C120EAC; Tue, 4 Oct 2022 09:24:37 -0400 (EDT) In-Reply-To: <83mtacw073.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 04 Oct 2022 09:51:44 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:296881 Archived-At: Eli Zaretskii [2022-10-04 09:51:44] wrote: >> Does anyone here have an idea why `getaddrinfo` might return an outdated >> error, or whether it could come from elsewhere? Or how/where I might >> find a kind of DNS cache that would be process-local rather >> than systemwide? > Is it certain that the problem is specific to that single process? No. But it's certain that it's not system-wide because all the other processes (including a fresh new Emacs session, and an older Emacs session that rarely/never uses network connections) I tried had no problem resolving that same address. It very definitely looks specific to that process. > Did you try flushing and renewing the system's DNS cache with the > appropriate shell commands? I don't know that I have such a thing on this system. Stefan