DNS rewrites don't work with subdomains of the same domain

[hauntedghost]

I'm looking for a way to setup DNS redirects from amazon.com to smile.amazon.com.
I currently have a DNS Rewrite setup with the following settings and the redirect is not sending me to the correct URL.

[agneevX]

Because that's not how DNS works? It allows you to set a custom IP, not a host name.

[ZeroClover]

Because that's not what a DNS server should do.

To do what you want, you need to run an HTTP server, then install your own Root CA for all clients in your network to implement MitM, and then resolve amazon.com to your HTTP server. Finally configure the HTTP Server to send HTTP redirects (HTTP 301 / 302 / 307 / 308).

[hauntedghost]

Understood. I guess I thought that would be the function of the dns server to forward the request to smile.amazon vs Amazon since Adguard home is a proxy server. Appreciate your help. I'll look into the mitm proxy.

…

On Sun, Dec 26, 2021, 2:34 PM ZeroClover ***@***.***> wrote: Because that's not what a DNS server should do. To do what you want, you need to run an HTTP server, then install your own Root CA for all clients in your network to implement MitM, and then resolve amazon.com to your HTTP server. Finally configure the HTTP Server to send HTTP redirects (HTTP 301 / 302 / 307 / 308). — Reply to this email directly, view it on GitHub <#4016 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFKSOA3IPAKPZ42Q5U5JSQTUS535VANCNFSM5KX5HVKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[EugeneOne1]

@hauntedghost, hello and thanks for the report. Looks like a bug actually. Consider using ||amazon.com^$dnsrewrite=NOERROR;CNAME;smile.amazon.com custom rule as a temporary workaround.

AGH doesn't support HTTP redirects, indeed, if the issue intends that.

[ainar-g]

The others are correct in their recommendations about the HTTP redirects, but the fact that a *.amazon.com → smile.amazon.com doesn't result in clients getting the correct CNAME of smile.amazon.com is definitely a bug. Will fix.

[ainar-g]

The issue with the incorrect CNAME rewrite to a subdomain should now be fixed on the edge channel. Once again, thanks for the report!