From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.6 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 1ECD11F8C6 for ; Wed, 1 Sep 2021 20:30:26 +0000 (UTC) Received: by mail-qt1-x835.google.com with SMTP id u21so874604qtw.8 for ; Wed, 01 Sep 2021 13:30:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mime-version:content-disposition; bh=D3KubuHxY4//NQVcKSZyhahsOSGClyTfm014yWRaMtk=; b=aTmrbm/Az0u80gB75yXn28pdwMlNAgn2T4+W0Wm/jyyBKiSKeGFzK5Agl3rXjq3Eqe Xw+MmFKCQLyo5Kv/015WDGJbBJ7soK6czyiyQX6DGBEF5nShsFxC5ddd6o1zvOvQZlpj wDSn/X3q1s7PfA3oYuLsbbNBXnJw2YtdC8Bh8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition; bh=D3KubuHxY4//NQVcKSZyhahsOSGClyTfm014yWRaMtk=; b=ior7NZYBn9oLsXqGNFBwKxqfHdHgLvjlto+w8IaaybVpIRFfCk7mPFsTmHjPsRRJGF PzmGbyp1jYh1LWwrOrRWLBNqAOeFtrt7kNboO3xk4fikLgMykjDW1fGvEBtr2sY9UH53 lHq2O7zVL+A1XYG857lXYTrvmwxSAwyVBlm4f/HD6TBV/A5MdhMf4z8ja4H2tmekRIkB s+qS/CYwHFzgHs8y+v/EtxtMJUjOKm9pAfMx4DFdIh1mkgmd4FlUCqwrmPBvYWTjpPnV 81u06YZTyELmuTMr0fbImZDK7T8kypILL/GPhBFzNZLKMLDQ7IJ8/FR7WXz2crdynIVU zJSg== X-Gm-Message-State: AOAM531g7AU7ebVbk0q0ZE3SwtI8P6P0UwfzkkLgwYk0CYseuVeZNVER Y+d37a0fxyS8smMYYhKdChkhsGgEEuqwW+uT X-Google-Smtp-Source: ABdhPJyc3fJAsr1pNwmv724NIremqBirnBpTu53S9k/ur9BgL6Qpi8UJZwpsgDK8vzs2i1JCdzevgQ== X-Received: by 2002:ac8:7761:: with SMTP id h1mr1300820qtu.272.1630528224139; Wed, 01 Sep 2021 13:30:24 -0700 (PDT) Received: from meerkat.local (bras-base-mtrlpq5031w-grc-32-216-209-220-181.dsl.bell.ca. [216.209.220.181]) by smtp.gmail.com with ESMTPSA id p15sm599155qti.70.2021.09.01.13.30.23 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 01 Sep 2021 13:30:23 -0700 (PDT) Date: Wed, 1 Sep 2021 16:30:22 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: Is it safe to round-robin the nntp server? Message-ID: <20210901203022.lmyudbbouxzt5rfr@meerkat.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Hello: With lore.kernel.org now 3 different nodes with failover, I'm curious if it's safe to point the NNTP server at that as well. I'm assuming that article numbers are going to be the same across all three systems, but I wanted to double-check that it's the case. I.e., if node1 goes down and DNS shifts to point at node2, will that mess up nntp access, or is that okay? What about imap? -K