Newsgroups: php.internals,php.pecl.dev,php.windows Path: news.php.net Xref: news.php.net php.internals:97832 php.pecl.dev:14440 php.windows:31439 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44055 invoked from network); 17 Jan 2017 21:07:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jan 2017 21:07:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.216 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.216 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.216] ([81.169.146.216:34509] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DC/4D-00729-7778E785 for ; Tue, 17 Jan 2017 16:07:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1484687220; l=3967; s=domk; d=kelunik.com; h=Content-Type:Cc:To:Subject:Date:From:References:In-Reply-To: MIME-Version; bh=zKVaUSKmTmBun3SDgEru+SknOa2jjzB5kHbHT5/jTo0=; b=REUw1Dk3d4kBd4SR6CHyetgd7uKj52KDqNtN/mj9hhz+OBZph+O9yGXh0oY77Djgci E1+k48KApYoSzM7lBzj8/Ma7Rz/zVpXsMOHkc/1IZKdz5G3mi4Pp3oJQ/dOLmLmH5SBO a7viUafysaAn2hLZGYsZ5iE0RM2KCQ/Nm+Vvg= X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mls2vWuiu+7SLDup6E67mzuoNJBqD/ufY= X-RZG-CLASS-ID: mo00 Received: from mail-qt0-f179.google.com ([209.85.216.179]) by smtp.strato.de (RZmta 39.11 AUTH) with ESMTPSA id J09854t0HL703VC (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp384r1 with 384 ECDH bits, eq. 7680 bits RSA)) (Client did not present a certificate); Tue, 17 Jan 2017 22:07:00 +0100 (CET) Received: by mail-qt0-f179.google.com with SMTP id k15so180390576qtg.3; Tue, 17 Jan 2017 13:07:00 -0800 (PST) X-Gm-Message-State: AIkVDXJUXahtaDQTiorV6vG2+ZZSO30dc8Y/OAI/0BuNg3MVDikKmgAIvwJIXyekosv6WcZjF3ghwrKd5qYcgg== X-Received: by 10.233.232.202 with SMTP id a193mr36900962qkg.113.1484687219812; Tue, 17 Jan 2017 13:06:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.144.132 with HTTP; Tue, 17 Jan 2017 13:06:59 -0800 (PST) In-Reply-To: <043801d270f5$ff3bc010$fdb34030$@belski.net> References: <043801d270f5$ff3bc010$fdb34030$@belski.net> Date: Tue, 17 Jan 2017 22:06:59 +0100 X-Gmail-Original-Message-ID: Message-ID: To: Anatol Belski Cc: PHP Internals , php-windows@lists.php.net, pecl-dev@lists.php.net, systems@php.net, Pierre Joye Content-Type: multipart/alternative; boundary=94eb2c033ce8570b62054650aecf Subject: Re: [PHP-DEV] windows.php.net is moving to new IP From: me@kelunik.com (Niklas Keller) --94eb2c033ce8570b62054650aecf Content-Type: text/plain; charset=UTF-8 > > Hi, > > I'm writing to inform, that the current Windows infrastructure hosting > sponsor doesn't plan to support the project anymore. Furthermore, a > notification was given, that the servers will be taken down within a couple > of next weeks. Alex Schoenmaker found another sponsor, so all the HW will > have to be moved to a new place. As a consequence, some shortages are to > expect. The particular date for the move is 3pm-4pm CET on Friday 20th > January. The downtime might concern windows.php.net downloads, snapshot > build uploads, as well as the PECL build and upload service. Especially as > the boxes have to be physically disconnected, a downtime of at least one > hour is possible. Please plan your possible work with accordance to this > info. > > This action requires some one of the devops to set the new A record and to > reload the DNS server configuration. I'm going to mail the new IP address > for the A record to systems@php.net close to the moment things are about > to > move. A temporary redirect is planned for the transition time, so then at > least the basic service should be back after the boxes are back online. > However, this redirect will likely to be only active only until the end of > January. Could please someone from the systems team give a confirmation, > the > record could be changed close to the move action? > > Thanks > > Anatol > Hi Anatol, if such a change is planned, the TTL for the DNS record should probably be adjusted to have a shorter caching of the old records. Regards, Niklas --94eb2c033ce8570b62054650aecf--