Invalid hostname provided to Image component in next/image configuration

When using the <Image> component to fetch assets from external sources, providing a remote URL not explicitly defined in the next.config.js file results in a render-time failure. This prevents the internal image optimizer from processing or serving the asset.

There is significant architectural ambiguity between utilizing the legacy images.domains array and the modern images.remotePatterns configuration. While remotePatterns allows for granular control over protocols, ports, and path patterns, the domains approach remains prevalent in existing codebases and tutorials.

Furthermore, the wildcard matching behavior within remotePatterns—specifically how multi-segment versus single-segment wildcards are handled—can lead to unexpected hostname rejections across different Next.js versions.

• What are the specific security implications of migrating from domains to remotePatterns in Next.js 14+
• How does wildcard matching logic differ for nested subdomains compared to top-level domains within the remotePatterns schema?