From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Chad Kimes <chkimes@github.com>
Subject: Re: www.cygwin.com DNS setup
Date: Thu, 14 May 2020 17:31:08 +0100 [thread overview]
Message-ID: <97e93adb-4782-40bc-d33c-00c27ed56b74@dronecode.org.uk> (raw)
In-Reply-To: <CABTKjsz75FkcPzEeKfZLB59O-j42jYXH2SqX1jDd-vxUoQDAmg@mail.gmail.com>
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.
next prev parent reply other threads:[~2020-05-14 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 15:54 Chad Kimes
2020-05-14 16:31 ` Jon Turney [this message]
2020-05-15 15:47 ` Chad Kimes
2020-05-20 13:38 ` Chad Kimes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97e93adb-4782-40bc-d33c-00c27ed56b74@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=chkimes@github.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).