X-Original-To: pgsql-www-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id DA3C49FA606 for ; Tue, 20 Jun 2006 01:34:06 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 63575-03 for ; Tue, 20 Jun 2006 01:34:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 8B6A69F9316 for ; Tue, 20 Jun 2006 01:34:00 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id k5K4Y2Q02608; Tue, 20 Jun 2006 00:34:02 -0400 (EDT) From: Bruce Momjian Message-Id: <200606200434.k5K4Y2Q02608@momjian.us> Subject: Archives site down again To: PostgreSQL www Date: Tue, 20 Jun 2006 00:34:02 -0400 (EDT) CC: "Joshua D. Drake" X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/45 X-Sequence-Number: 10201 http://archives.postgresql.org is showing unreachable again for me, the third time in the past week for me. A discussion on IRC below stated one of the commandprompt DNS servers wasn't reliable. Can this be corrected? --------------------------------------------------------------------------- bmomjian: strange bmomjian: dig returns: bmomjian: archives.postgresql.org. 4h15m14s IN CNAME pgsql-archives.commandprompt.com. DB_Home: if you dig archives.postgresql.org what do you get bmomjian: but traceroute still fails DB_Home: and if you dig pgsql-archives.commandprompt.com applejack: bmomjian, and whet does dig pgsql-archives.commandprompt.com return? bmomjian: so it is the commandprompt DNS that is messed up bmomjian: nothing Andrew, Supernews: seems fine from here DB_Home: traceroute to 69.55.229.115 bmomjian: (2) dig www.commandprompt.com. bmomjian: fails Andrew, Supernews: ah, I see: DB_Home: and 207.173.200.12 Andrew, Supernews: 40.0% of queries will end in failure at 69.55.229.115 (ns1.cmdalert.com) - returned SERVFAIL code Andrew, Supernews: 40.0% of queries will be returned by 207.173.200.129 (ns1.commandprompt.com) Andrew, Supernews: pgsql-archives.commandprompt.com.600INA207.173.200.133 Andrew, Supernews: 20.0% of queries will be returned by 200.46.204.254 (ns3.hub.org) Andrew, Supernews: pgsql-archives.commandprompt.com.53INA207.173.200.133 Andrew, Supernews: that's from the squish.net/dnscheck checker FastJack left the room (quit: Connection timed out). scardinal [n=supreme@port816.ds1-suoe.adsl.cybercity.dk] entered the room. bmomjian: oh, now it works DB_Home: so the probelm is ns1.cmdalert.com is not reliable Andrew, Supernews: so one of commandprompt's dns servers is down bmomjian: seems so, can someone email Drake those details. I don't get that from here Andrew, Supernews: well, not down, but lame -- Bruce Momjian http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +