Click & destination
Dynamic DNS
- Ad Manager API value
- DYNAMIC_DNS
What Google's rule says
The Ad Manager API defines DYNAMIC_DNS as the landing page for the creative using a dynamic DNS. Google's rejected-creatives guidance lists the use of dynamic DNS to switch page or ad content among the behaviours it treats as gaming the network.
What actually causes it
- A landing page hosted on a dynamic DNS provider, which is common in small or temporary setups.
- A destination whose address changes between the review and the serve.
- An affiliate or white-label host that rotates its origins.
- Infrastructure genuinely built to show reviewers one page and users another.
How to fix it
Move the landing page to a stable hostname with a fixed origin. There is no configuration that makes a dynamic DNS destination acceptable, so this is a hosting change rather than a creative one.
The part that is not obvious
Dynamic DNS is the one reason on this list that is judged on infrastructure rather than on anything the creative does or shows. That makes it strict-liability in practice: a legitimate advertiser on a small host can trip it without any intent, because the property Google objects to is that the address can be repointed after review, not that it has been. The corollary is that no amount of tidying the creative will help, and an appeal has to be a change of hosting.
Related reasons
Reason name and API value verified against Ad Manager API — CreativePolicyViolation (v202602) on 30 July 2026 (Ad Manager SOAP API v202602). The causes and fix above are practitioner guidance, not Google policy text.