W3 Total Cache and MaxCDN Custom Domain Issue [No Zones Matching Custom Domain]
Previous versions of W3 Total Cache and MaxCDN I was able to have defined cdn1.dragonblogger.com, cdn2.dragonblogger.com…etc as cname defined in the “Replace site’s hostname with:”
But ever since converting to the Consumer Key/Consumer Secret method, it can only use the actual MaxCDN Pull Zone DNS record, even with having my custom CName records defined, I can’t put any of them in W3 Total Cache CDN configuration or I get an error No Zones Matching Custom Domain. It is like it doesn’t check MaxCDN to actually see which CNAMES are added to the pull zone and compare, it only wants to look at the primary MaxCDN DNS record for the pull zone.
- The topic ‘W3 Total Cache and MaxCDN Custom Domain Issue [No Zones Matching Custom Domain]’ is closed to new replies.