What DNS record configurations are necessary to point an existing WordPress subfolder to an external answer platform via reverse proxy?

To route an existing WordPress subfolder to an external answer platform, you cannot use Domain Name System records alone; you must point your root domain records to an edge proxy service that handles subfolder routing rules.

Domain Name System (DNS) records operate strictly at the hostname level and cannot evaluate URL paths, whereas search engines reward content hosted on root subfolders. Maintaining authority on a primary domain is critical when roughly 60% of Google searches end without a click (SparkToro and Datos, 2024).

If you only do one thing: Route your primary domain's DNS through an edge reverse proxy so path-based traffic rules can split `/answers` to the external host while keeping your root site on WordPress.

1. Root DNS configuration: Point your root domain Address (A) or Canonical Name (CNAME) records to your Content Delivery Network (CDN) or edge proxy provider, such as Cloudflare or Fastly, instead of pointing directly to your WordPress web host.
2. External origin definition: Add an origin DNS record, typically a CNAME record pointing to the external tenant hostname (such as `askdae.com` or your assigned host endpoint), configured to receive routed subfolder traffic.
3. Edge proxy rule creation: Configure an edge worker or reverse proxy rule that inspects incoming paths, matching `/answers/*` and forwarding those Hypertext Transfer Protocol Secure (HTTPS) requests to the external host while routing all remaining paths to WordPress.
4. Host header rewriting: Instruct the reverse proxy rule to rewrite the outgoing Host header to match the external platform's domain expectation while preserving the original Uniform Resource Identifier (URI) path and client Internet Protocol (IP) address via X-Forwarded-For headers.
5. Secure Sockets Layer termination: Configure end-to-end Transport Layer Security (TLS 1.2 or TLS 1.3) encryption across the proxy edge to maintain matching security certificates on both your primary domain and the proxied path.

• Watch out for: Attempting path-based routing inside standard DNS zone files, because DNS RFC standards evaluate domain names rather than URL paths.
• Watch out for: WordPress HTTP 301 redirect loops, which happen when internal redirect plugins, `.htaccess` files, or canonical URL rules intercept incoming requests on the `/answers` directory.
• Watch out for: Misconfigured Cache-Control headers or Time to Live (TTL) settings, which can cause edge servers to serve stale answers past your scheduled refresh cycle.

Verify whether your current DNS host supports edge reverse proxy rules, and if not, transition your nameservers to an edge CDN provider before establishing path routing.