sub-domains that are obsolete with 410

joshism

Hello, community support,

I used to have a service called gtranslate.io business plan with sub-domain features for translating text. I have removed this and set up lots of 410s on those domains for Google to deindex over time naturally.

The issue is that ezoic replaced all of these; while it is not breaking anything technically, it plagues the analytics and cache hit rates with poor performance when there shouldn't be, which makes it hard to see things.

Ideally, I want to return those to my host, but Ezoic keeps changing those DNS records around automatically after 5 to 15 minutes. So technically, it will cause long-term issues on other things besides analytics, leap cache ratio like Niche IQ suggestions, etc, and probably more.

Is there something I can do about this? Sadly I will probably need to keep these obsolete domains active for 12 to 24 months as per Google's recommendations when getting rid of content.

Keen on any ideas if there are.

Cheers.

Mark_P

Hey!

Thanks for reaching out. Sorry to hear that you are experiencing these issues.

When you are changing your DNS records where exactly are you changing them? at Ezoic or at your hosting provider?

This will give us a better indication as to the cause of this issue.

Thanks!

joshism

Mark_P

Thanks for the reply.

Nothing to do with hosting it's ezoic auto changing any dns records I set in cloud flare dns settings it will revert back to cname g.ezoic.net.

Also I run my own servers, everything is manually done, basically no third party involved. The only thing doing any auto setup is ezoic, this is why I was asking as in 5 mins setting the cname back to a record and my server I.p for let's say de.example.com it resets it back to the cname g.ezoic.net.

Hope this makes a bit more sense. The only other idea is that I need to edit things in ezoic dns manager?

Monica

Hi there! When integrated with Ezoic via the Cloudflare method, Ezoic is acting as the main proxy for your site rather than Cloudflare. This means that any DNS updates required to match the records found at the host need to be made within the Ezoic Dashboard first (Ezoic Dashboard > Settings > DNS Records). These changes will then automatically propagate into Cloudflare.

Note: Making changes to the DNS records in Cloudflare does not work, as any changes made at Cloudflare would just be overwritten by Ezoic.

Try navigating to the DNS Records located at Ezoic to make your changes, and let us know if you need further assistance!

joshism

Monica

Hi,

I've resolved the issue, and you were correct about the initial Ezoic DNS setting change, so thanks for that.

In essence, I removed 103 sub-domains from Ezoic. Then, I used Cloudflare's export feature, excluded both .example.com and www.example.com from the list, and replaced all instances of g.ezoic.net with my IP address. I also changed the CNAME to an A record and uploaded everything in bulk. The process was seamless.

It's worth noting that any DNS adjustments made within Ezoic's settings will be reflected in Cloudflare. For instance, if I were to add news.example.com to create a new subsection, it would remove those 100+ multilingual sub-domains. However, if users are proactive and maintain a backup list, they can quickly upload it to Cloudflare. This ensures a swift return to the original settings.

I wanted to share this information with anyone encountering a similar situation. It's not a typical scenario, but this feedback could benefit you and others.

Thanks again.

AnyaR

Hi there,
Thank you for sharing the additional information and further explanation of the situation 🙂 We aim for the Community to be a ressource where publishers can not only reach out for assistance but also find similar threads on issues that they are currently facing, and publishers such as yourself sharing their experience greatly contributes to this goal!