Re: www unreachable
It's not working i DK either. Med Venlig Hilsen / Best Regards Henrik Krysteli Semark Mobil: +45 2633 1701 On 15/06/2020 13.01, Chris Bennett wrote: > On Mon, Jun 15, 2020 at 12:19:09PM +0200, Anders Andersson wrote: >> Are you saying it's working for you? Maybe you have a different route >> to the website because it seems to be down on the Canadian side. I >> presume you're in the US based on your domain name. :) > No, it's not working for me either. > I'm in Austin, TX and not working from my server in Chicago either. > > Chris Bennett > >
Re: www unreachable
On Mon, Jun 15, 2020 at 12:19:09PM +0200, Anders Andersson wrote: > > Are you saying it's working for you? Maybe you have a different route > to the website because it seems to be down on the Canadian side. I > presume you're in the US based on your domain name. :) No, it's not working for me either. I'm in Austin, TX and not working from my server in Chicago either. Chris Bennett
Re: www unreachable
On 2020-06-15 10:53 +0100, Tom Smyth wrote: > > It is not accessible from virgin media in Ireland either, > not connecting on 80 or 443 TCP ... via telnet... > dns is resolving Not from Oslo, Norway either ... traceroute to openbsd.org (129.128.5.194), 30 hops max, 60 byte packets 8 nix-ix.core1.osl1.he.net (185.1.55.90) 1.117 ms 1.082 ms 1.117 ms 9 100ge8-1.core1.sto1.he.net (184.105.64.229) 7.741 ms 7.704 ms 7.706 ms 10 100ge8-2.core1.ams1.he.net (184.105.65.125) 26.893 ms 27.931 ms 27.855 ms 11 100ge16-1.core1.lon2.he.net (72.52.92.213) 39.193 ms 32.692 ms 32.658 ms 12 * * 100ge13-2.core1.nyc4.he.net (72.52.92.166) 101.286 ms 13 100ge14-1.core1.tor1.he.net (184.105.80.10) 111.240 ms 110.175 ms 110.727 ms 14 100ge6-1.core1.ywg1.he.net (184.105.64.102) 131.352 ms 130.307 ms 129.769 ms 15 100ge5-2.core1.yxe1.he.net (184.104.192.70) 140.816 ms 138.105 ms 141.801 ms 16 100ge11-2.core1.yeg1.he.net (72.52.92.61) 145.821 ms 145.975 ms 145.742 ms 17 * university-of-alberta-sms.10gigabitethernet2-2.core1.yeg1.he.net (184.105.18.50) 149.379 ms 147.342 ms 18 cabcore-esqgw.corenet.ualberta.ca (129.128.255.35) 146.425 ms katzcore-esqgw.corenet.ualberta.ca (129.128.255.41) 147.156 ms 148.021 ms 19 * * * 20 * * * 21 * * * 22 obsd3.srv.ualberta.ca (129.128.5.194) 858.107 ms 743.906 ms 743.194 ms signature.asc Description: PGP signature
Re: www unreachable
On Mon, Jun 15, 2020 at 11:45 AM Chris Bennett wrote: > > On Mon, Jun 15, 2020 at 09:43:03AM +0200, Thomas de Grivel wrote: > > Hello, > > > > http://www.openbsd.org is unreachable. > > > > I wanted to know what's new in the current snapshots ? > > > > I'm not sure about the website. You might have local DNS problems. > Use dig to get the IP address (from a big nameserver like 8.8.8.8) > and skip that problem. > > If you mean the current -release, yes the website is simplest in > general terms only. > > If you mean -current, then the mailing lists and CVS are the right > places to look. misc@ isn't very helpful, but tech@, etc. are excellent. > > > DNS has problems in some places in the world. Usually just for hours. > Annoying, but sites like OpenBSD have stable IP's and knowing that > solves the problem quickly. > If the site has a problem, someone else can clarify that. > > Chris Bennett Are you saying it's working for you? Maybe you have a different route to the website because it seems to be down on the Canadian side. I presume you're in the US based on your domain name. :)
Re: www unreachable
On Mon, 15 Jun 2020, Chris Bennett wrote: > On Mon, Jun 15, 2020 at 09:43:03AM +0200, Thomas de Grivel wrote: > > Hello, > > > > http://www.openbsd.org is unreachable. > > > > I wanted to know what's new in the current snapshots ? > > > > I'm not sure about the website. You might have local DNS problems. > Use dig to get the IP address (from a big nameserver like 8.8.8.8) > and skip that problem. > > If you mean the current -release, yes the website is simplest in > general terms only. > > If you mean -current, then the mailing lists and CVS are the right > places to look. misc@ isn't very helpful, but tech@, etc. are excellent. > > > DNS has problems in some places in the world. Usually just for hours. > Annoying, but sites like OpenBSD have stable IP's and knowing that > solves the problem quickly. > If the site has a problem, someone else can clarify that. > > Chris Bennett It seems to be non-reachable indeed. As far as I can see is not a DNS issue. And most likely whoever needs to know already knows. If you need to access the website you have 2 easy options: * clone the www cvs source repository and serve it locally (via local httpd or just a simple `python3 -m http.server`). Best option in my opinion. * use a mirror. Recently solene@ built one for circumstances like this: https://perso.pw/www.openbsd.org/ And here's another one managed by clematis: https://openbsd.clemat.is/ Keep in mind that those mirrors are not official and may be out of sync. Cheers, -- Paco Esteban. 0x5818130B8A6DBC03
Re: www unreachable
It is not accessible from virgin media in Ireland either, not connecting on 80 or 443 TCP ... via telnet... dns is resolving Tracing route to openbsd.org [129.128.5.194] over a maximum of 30 hops: 4 8 ms 5 ms 7 ms 109.255.249.254 528 ms23 ms22 ms 84.116.239.10 617 ms17 ms16 ms 84.116.238.62 7 *** Request timed out. 816 ms17 ms18 ms 84.116.135.46 923 ms21 ms20 ms 84.116.135.69 1019 ms19 ms34 ms 216.66.80.117 1185 ms85 ms82 ms 72.52.92.166 1295 ms95 ms97 ms 184.105.80.10 13 115 ms 117 ms 115 ms 184.105.64.102 14 122 ms 122 ms 123 ms 184.104.192.70 15 133 ms 134 ms 131 ms 72.52.92.61 16 130 ms 130 ms 130 ms 184.105.18.50 17 135 ms 128 ms 129 ms 129.128.255.41 18 *** Request timed out. 19 *** Request timed out. 20 *** Request timed out. 21 133 ms 189 ms 741 ms 129.128.5.194 On Mon, 15 Jun 2020 at 10:50, Chris Bennett wrote: > On Mon, Jun 15, 2020 at 09:43:03AM +0200, Thomas de Grivel wrote: > > Hello, > > > > http://www.openbsd.org is unreachable. > > > > I wanted to know what's new in the current snapshots ? > > > > I'm not sure about the website. You might have local DNS problems. > Use dig to get the IP address (from a big nameserver like 8.8.8.8) > and skip that problem. > > If you mean the current -release, yes the website is simplest in > general terms only. > > If you mean -current, then the mailing lists and CVS are the right > places to look. misc@ isn't very helpful, but tech@, etc. are excellent. > > > DNS has problems in some places in the world. Usually just for hours. > Annoying, but sites like OpenBSD have stable IP's and knowing that > solves the problem quickly. > If the site has a problem, someone else can clarify that. > > Chris Bennett > > > -- Kindest regards, Tom Smyth.
Re: www unreachable
On Mon, Jun 15, 2020 at 09:43:03AM +0200, Thomas de Grivel wrote: > Hello, > > http://www.openbsd.org is unreachable. > > I wanted to know what's new in the current snapshots ? > I'm not sure about the website. You might have local DNS problems. Use dig to get the IP address (from a big nameserver like 8.8.8.8) and skip that problem. If you mean the current -release, yes the website is simplest in general terms only. If you mean -current, then the mailing lists and CVS are the right places to look. misc@ isn't very helpful, but tech@, etc. are excellent. DNS has problems in some places in the world. Usually just for hours. Annoying, but sites like OpenBSD have stable IP's and knowing that solves the problem quickly. If the site has a problem, someone else can clarify that. Chris Bennett
www unreachable
Hello, http://www.openbsd.org is unreachable. I wanted to know what's new in the current snapshots ? -- Thomas de Grivel kmx.io
