From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) by sourceware.org (Postfix) with ESMTPS id 25346395C41A for ; Wed, 20 May 2020 13:38:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 25346395C41A Received: by mail-io1-xd35.google.com with SMTP id o5so3100930iow.8 for ; Wed, 20 May 2020 06:38:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=G4EaDql/a63qFC64mNuYkApNI4UNjtYs5rDm5+IIhSs=; b=WGQwPLUUBADruKvDbGbWDCziUqyHMPt1jwZcXpNrhro8rCpnH1wHXd1+s0BI3Rp9MJ VXq9Suipvb/zL/cKMwF/NNCR1mfFoqIs6WKt6zFkr38yCWSfnSdEYAgnS3fDjAxx3nvf 3OsSLKDjbK5smMXCkX2Lflw9UCKli/D8lRKkKmlToS1R2aghXkyRxnFR8HnYiiSgoL3d ONUzZibncvNytGRWp8HUPS+4j0twnmWhL5ixKbvqUHGMB8Jcc2JhU69nhDnh5Vig+aP2 92GiM3k3EOaoICwh5kjuWZWs1+2MKqzsrPkGXD0KvTYmWxmH1vLdw1qJqNQir9WOg7h4 jzoA== X-Gm-Message-State: AOAM533y5xhtDV4jYuI8fKdOzqAAzKtmWx614QbmFq+7ZlKp8A9S2r3w hnYOnT1bgKqLrQc+C7T21FIOQ7s+riDbCzLFrv+A8Sb9 X-Google-Smtp-Source: ABdhPJwFD4wzlCI78lgzkdZ555Bc2EDguEMxX4sOBDNLLCXFyzh5afNT7QvCAurYvWAnRu2sdHtGuzSR/rh4iDa+GAE= X-Received: by 2002:a05:6638:ca1:: with SMTP id x1mr4334806jad.86.1589981893365; Wed, 20 May 2020 06:38:13 -0700 (PDT) MIME-Version: 1.0 References: <97e93adb-4782-40bc-d33c-00c27ed56b74@dronecode.org.uk> In-Reply-To: From: Chad Kimes Date: Wed, 20 May 2020 09:38:01 -0400 Message-ID: Subject: Re: www.cygwin.com DNS setup To: Jon Turney Cc: The Cygwin Mailing List X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TVD_PH_BODY_ACCOUNTS_PRE, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2020 13:38:15 -0000 Hi all - gentle ping here. I want to make sure Cygwin doesn't have any issues with IPv6 connectivity after this change. Could you look into suggesting the above AAAA record to the responsible team? Thanks! -Chad On Fri, May 15, 2020 at 11:47 AM Chad Kimes wrote: > Thanks Jon! > > I see the change went through and I re-ran my validation script a few > times and I don't see the error anymore, which is awesome. > > However, I believe my suggestions have inadvertently broken IPv6 > connectivity for www.cygwin.com! The CNAME accounts for both A and AAAA > records, but only an A record was added after the CNAME was removed. > > To fix this, can you please suggest that the team add an AAAA record > pointing to 2620:52:3:1:0:246e:9693:128c (the address for > server2.sourceware.org)? > > Thanks, > -Chad > > On Thu, May 14, 2020 at 12:31 PM Jon Turney > wrote: > >> On 14/05/2020 16:54, Chad Kimes via Cygwin wrote: >> > Hi all, >> > >> > I'm investigating an issue with GitHub Actions runners having issues >> > connecting to www.cygwin.com: >> > https://github.com/actions/virtual-environments/issues/698 >> > >> > I worked with the Azure DNS team and in this comment >> > < >> https://github.com/actions/virtual-environments/issues/698#issuecomment-628284472 >> > >> > I >> > detail what we believe to be the likely issue. Summarized: >> > >> > www.cygwin.com is CNAME'd to server2.sourceware.org >> > server2.sourceware.org is an NS server for sourceware.org >> > >> > We believe that the above configuration is triggering a bug in WinDNS >> that >> > is causing intermittent DNS resolution failures. I don't have an ETA for >> > resolution from the Azure DNS team, and internally I'm translating that >> to >> > be on the order of months before we see a fix. In order to resolve this >> > faster for customers, I'm reaching out to see what options we have for >> > updating the DNS records that are triggering this bug. >> > >> > Is there a change you can make to either www.cygwin.com or >> > server2.sourceware.org DNS such that it doesn't have this recursive >> > reference issue? Some options are to replace the CNAME with an A >> record, or >> > to use something like ns2.sourceware.org for the NS record instead of >> > server2.sourceware.org which is being used for cygwin's A record >> reference. >> >> I have drawn the attention of sourceware overseers to this. >> >> They have requested the DNS change you suggest. >> >