Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org

Following up on Perlmonks.com and Perlmonks.net to redirect to Perlmonks.org

Thanks to the support of Leo Lapworth, Olaf Alders, and Robert from Perl NOC, this site is now served from behind the Fastly CDN. The IP addresses have changed to Fastly IP addresses.

The .com and .net domains redirect to perlmonks.org, to improve the caching of the pages.

If you access the site logged in, you should see no difference, as the pages pass through directly to the main machines.
Anonymous access should also be mostly unchanged except for AI scrapers.

If you notice any adverse changes, please post a reply here.

*Credit on our side goes to the irreplaceable Co-rion.

Comment on Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org

Replies are listed 'Best First'.
Re: Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org by syphilis (Archbishop) on May 15, 2026 at 03:09 UTC
If you notice any adverse changes, please post a reply here. When attempting to access a node, I intermittently get: `Error 503 Backend unavailable, connection timeout Backend unavailable, connection timeout Error 54113 Details: cache-wsi-ysbk1060063-WSI 1778814214 2084897532 Varnish cache server` [download] Cheers, Rob	[reply] [d/l]
Re^2: Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org by Corion (Patriarch) on May 15, 2026 at 05:59 UTC
These errors come when the backend is overloaded. This problem still happens, since now the TCP ports are not exhausted anymore, but the bots are still hitting the site a lot and the caching on Fastlys side is not yet there/set up well enough to give these bots a good answer. We reject them more quickly and now hit 40 requests/s easily, but that does not mean that logged-in users always get a connection to the backend unfortunately.	[reply]
Re^3: Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org by hippo (Archbishop) on May 15, 2026 at 12:35 UTC
It might also be the case that all the bad bots are "doing a Yahoo" and caching the old DNS for much longer than the TTL and therefore still hitting the origin servers directly. Might be worth asking Pair to restrict access to those (at the firewall level) only from Fastly sources. 🦛	[reply]
Re^2: Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org by eyepopslikeamosquito (Archbishop) on May 15, 2026 at 03:37 UTC
Yes, I'm also seeing the same error quite a lot. For example: `Error 503 Backend unavailable, connection timeout Backend unavailable, connection timeout Error 54113 Details: cache-mel11252-MEL 1778815557 3830543164 Varnish cache server` [download] Update: got this similar one when voting on a node: `Error 503 Resource temporarily unavailable Resource temporarily unavailable Error 54113 Details: cache-mel11279-MEL 1778820406 2833676408 Varnish cache server` [download] Update: another similar one: `Error 503 first byte timeout first byte timeout Error 54113 Details: cache-mel11226-MEL 1778826805 3169835228 Varnish cache server` [download] 👁️🍾👍🦟	[reply] [d/l] [select]
Re^2: Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org by roho (Bishop) on May 15, 2026 at 04:42 UTC
I am seeing the same error message. `Error 503 Resource temporarily unavailable Resource temporarily unavailable Error 54113 Details: cache-pdk-kpdk2140043-PDK 1778819728 1898921539 Varnish cache server` [download] "It's not how hard you work, it's how much you get done."	[reply] [d/l]