docs: Update link

Author: amannn

docs/src/pages/blog/next-intl-4-0.mdx

@@ -218,7 +218,7 @@ To make it easier to work with error handling functions on the client side, `Nex
 
 ## Stricter config for `domains` [#domains-config]
 
-So far, when using [`domains`](/docs/routing#domains) in combination with [`localePrefix: 'as-needed'`](/docs/routing#locale-prefix-as-needed), `next-intl` had to make some [tradeoffs](https://next-intl-docs-6wwcmwb9a-next-intl.vercel.app/docs/routing#domains-localeprefix-asneeded) to avoid reading the current host of the incoming request in components.
+So far, when using [`domains`](/docs/routing#domains) in combination with [`localePrefix: 'as-needed'`](/docs/routing#locale-prefix-as-needed), `next-intl` had to make some [tradeoffs](https://v3.next-intl.dev/docs/routing#domains-localeprefix-asneeded) to avoid reading the current host of the incoming request in components.
 
 Now, by introducing two new constraints, `next-intl` can avoid these tradeoffs altogether: