Redirects cached?

Support
1

Hey Team, I have two Netlify projects in question here.

Originally I was sending multiple domains to just one of those two domains with a _redirect file and have since updated the DNS and redirect of the second domain to point to a the new project but its still redirecting to the original project. Some details below.

What we want
connellypartners.com => [cp-com-3.netlify.app]
connellypartnersdublin.com => [cpdublin-com-3.app]

What is happening
connellypartners.com => [cp-com-3.netlify.app]
connellypartnersdublin.com => [cp-com-3.netlify.app]

Again, up until this week this was by design and this was happening because the DNS for connellypartnersdublin.com was pointing at cp-com-3.netlify.app and using a redirect [below] to forward that request over to connellypartners.com. I have since changed the DNS and removed the redirect in question but the connellypartnersdublin.com is still resolving to connellypartners.com

I’ve tried clearing my dns cache and using another computer to ensure its not a local cache

DNS results for connellypartners.com

dig connellypartners.com
;; ANSWER SECTION:
www.connellypartners.com. 300 IN CNAME cp-com-3.netlify.com.
cp-com-3.netlify.com. 20 IN A 162.243.166.170
cp-com-3.netlify.com. 20 IN A 159.65.216.232

DNS for connellypartnersdublin.com

dig www.connellypartnersdublin.com
;; ANSWER SECTION:
www.connellypartnersdublin.com.	300 IN	CNAME	cpdublin-com-3.netlify.app.
cpdublin-com-3.netlify.app. 20 IN A 104.248.50.87 
cpdublin-com-3.netlify.app. 20 IN A 159.65.216.232

My Redirect file.

# These rules will change if you change your site’s custom domains or HTTPS settings

# Redirect domain aliases to primary domain
# Old Dublin Redirects, commented out
# https://www.connellypartnersdublin.com/* https://www.connellypartners.com/:splat 301!
# https://connellypartnersdublin.com/* https://www.connellypartners.com/:splat 301!

# Optional: Redirect default Netlify subdomain to primary domain
https://cp-com-3.netlify.com/* https://www.connellypartners.com/:splat 301!

Any thoughts are greatly appreciated.

2

Hi, @ewebster, the redirect is happening because the following rule is in _redirects:

https://www.connellypartnersdublin.com/* https://www.connellypartners.com/:splat 301!
https://connellypartnersdublin.com/* https://www.connellypartners.com/:splat 301!

You can see the files deployed for the site to confirm here:

https://app.netlify.com/sites/cpdublin-com-3/deploys/5f3e956aa968e66cfac75d45

There is a button on that page to download the files which were part of that deploy shown in the screenshot below:

download-deploy-button-small

So, it isn’t that the redirects are cached; the current deploy contains that rule.

Also, that is a deploy from August. There are newer deploys but they are not being automatically published because that is only done for deploys to the branch master and this deploy above is for a different branch. It was manually made the production deploy with the “publish deploy” button on that page.

There is a newer deploy of that branch here:

https://app.netlify.com/sites/cpdublin-com-3/deploys/5f5bc9b7bf9788000776d236

However, that deploy isn’t published so the site doesn’t reflect the changes there. The deploy above doesn’t contain that redirect so publish it would likely be all that is needed to resolve this.

You can also make deploys to this branch auto-publish if you make that branch the production branch for this site (which can be done here). In other words, if dev was the production branch there, changes to dev would automatically update the site.

If there are other questions and/or if this doesn’t resolve the issue, please let us know. (Last but not least, this is a Pro level team so please feel free to open support tickets if you prefer. This account does include that type of support.)