DNS setting and origin error

afrimaster

Dear Ezoic Support Team,

I hope this message finds you well. I am writing to seek your assistance with an ongoing issue I am facing regarding the DNS settings and Ezoic ads on afrimasterweb.com. I kindly request your prompt attention and support in resolving this matter.

Recently, I encountered an origin error related to the DNS settings of my website, afrimasterweb.com. As a temporary solution, I had to repoint the site to its host, which partially resolved the issue. However, upon repointing it back to Ezoic, I experienced a further setback, with the Ezoic ads ceasing to serve on the website. This unintended outcome has resulted in a significant decrease in ad revenue.

I am reaching out to you today with the hope that you can assist me in resolving this problem and restoring the proper functionality of Ezoic ads on afrimasterweb.com. Your expertise and guidance would be invaluable in identifying and rectifying the underlying issues causing the ads to stop serving.

Sincerely,

Bonaveture E

Chelsea_W

afrimaster Hi there,
Hope you are well. I can see as you mentioned some DNS settings have changed recently.

To start with i would suggest that you add back in and update your Ezoic DNS settings to match those at your host. Ezoic needs these to match your host so we can pull the site correct and ensure all is functioning as it should.

You will first need to grab your records from your host. Here is a guide on where you may be able to find them: Where to Find DNS Records / Zone Files at your Host

Once you have found these please go to your Ezoic DNS settings and add in the records to Ezoic: How To Update / Add DNS Records and Subdomains
You will want to add all A, CNAME, TXT, MX records and anymore that affect your site.
< image.png >

If after these are updated and you are still seeing an origin error please check out this guide: https://support.ezoic.com/kb/article/how-to-fix-origin-errors

If you are no longer seeing an error but are seeing Ads are not showing check out this Guide: Why Aren't Ads Showing Up On My Site?

afrimaster

Here is the record I have
DNS Record Summary

(edit removing DNS records from public view)

Chelsea_W

afrimaster These have been updated in your Ezoic account. I am seeing some of the site running on Ezoic. Can I ask you to please disable any other caching you have on the site? i am seeing a cache being used when viewing the headers on pages where Ezoic is not working and this could be the cause.

afrimaster

Thanks; I have done that and many other things, but the problem is still there. PLEASE I need help to resolve this origin error

cjsmith

Hi! Just to reassure you, the issue doesn't look widespread as I'm able to load your site just fine from my end and the site is currently passing global uptime tests as well. Intermittent origin errors are almost always caused by the host or a security plugin misinterpreting requests coming from Ezoic as bot traffic and subsequently blocking them. Fortunately this is almost always easily fixed by having your host whitelist the static IPs listed here: https://support.ezoic.com/kb/article/how-to-fix-origin-errors

Please let us know once they have done so, so that we can route your site via those IP addresses from this end - until we do, the issue will not be fully resolved. If your host will not whitelist the above IP addresses for some reason, they can try implementing one of the alternative suggestions listed in the article. Could you also let me know whether you have any security plugins installed such as Apache, Jetpack Protect, Wordfence, BitNinja, ModSecurity etc.?

afrimaster

Hello Bonaventure,

The IPs are allowed earlier, however they are in mass blocklists worldwide. I am attaching the log :

filter GDENYIN 1075 16 960 DROP tcp -- !lo * 52.20.0.0/14 0.0.0.0/0 multiport dports 80,443
IPSET: Set:bl_GREENSNOW Match:52.20.63.25 Setting:GREENSNOW file:/etc/csf/csf.blocklists
IPSET: Set:bl_GREENSNOW Match:3.225.202.138 Setting:GREENSNOW file:/etc/csf/csf.blocklists
IPSET: Set:bl_GREENSNOW Match:3.217.200.190 Setting:GREENSNOW file:/etc/csf/csf.blocklists
IPSET: Set:bl_GREENSNOW Match:54.212.71.227 Setting:GREENSNOW file:/etc/csf/csf.blocklists
filter GDENYIN 1070 0 0 DROP tcp -- !lo * 52.12.0.0/15 0.0.0.0/0 multiport dports 80,443
IPSET: Set:bl_GREENSNOW Match:52.12.170.68 Setting:GREENSNOW file:/etc/csf/csf.blocklists
filter GDENYIN 1043 25 1500 DROP tcp -- !lo * 34.208.0.0/12 0.0.0.0/0 multiport dports 80,443
IPSET: Set:bl_GREENSNOW Match:34.218.21.81 Setting:GREENSNOW file:/etc/csf/csf.blocklists
filter GDENYIN 1011 0 0 DROP tcp -- !lo * 13.126.0.0/15 0.0.0.0/0 multiport dports 80,443
IPSET: Set:bl_GREENSNOW Match:18.139.6.69 Setting:GREENSNOW file:/etc/csf/csf.blocklists
IPSET: Set:bl_GREENSNOW Match:18.140.184.0 Setting:GREENSNOW file:/etc/csf/csf.blocklists
filter GDENYIN 1017 0 0 DROP tcp -- !lo * 13.236.0.0/14 0.0.0.0/0 multiport dports 80,443
IPSET: Set:bl_GREENSNOW Match:18.157.131.187 Setting:GREENSNOW file:/etc/csf/csf.blocklists
IPSET: Set:bl_GREENSNOW Match:18.157.105.182 Setting:GREENSNOW file:/etc/csf/csf.blocklists
IPSET: Set:bl_GREENSNOW Match:3.126.25.160 Setting:GREENSNOW file:/etc/csf/csf.blocklists
IPSET: Set:bl_GREENSNOW Match:34.248.174.237 Setting:GREENSNOW file:/etc/csf/csf.blocklists
filter GDENYIN 1073 0 0 DROP tcp -- !lo * 52.16.0.0/15 0.0.0.0/0 multiport dports 80,443
IPSET: Set:bl_GREENSNOW Match:34.255.61.232 Setting:GREENSNOW file:/etc/csf/csf.blocklists
IPSET: Set:bl_GREENSNOW Match:15.236.165.82 Setting:GREENSNOW file:/etc/csf/csf.blocklists
IPSET: Set:bl_GREENSNOW Match:15.236.166.30 Setting:GREENSNOW file:/etc/csf/csf.blocklists
filter GDENYIN 1036 0 0 DROP tcp -- !lo * 18.228.0.0/16 0.0.0.0/0 multiport dports 80,443
filter GDENYIN 1036 0 0 DROP tcp -- !lo * 18.228.0.0/16 0.0.0.0/0 multiport dports 80,443
You might want to contact them back to request the delist since we cannot remove the blocklists for a shared server. Does in Gdeny are ours , so we will remove them, once they remove the rest.

Lindsey_

Hi there - Lindsey here. I hope you're well!

Thank you for sending this over. I've gone ahead and added you to our shortlist of IP's which should help in this respect.

However, as it sounds like your host is unable to whitelist our IP's due to a shared server, it may be best to ask that they action one of the other options mentioned in this article here: https://support.ezoic.com/kb/article/how-to-fix-origin-errors

Can you please see if a) the origin error is still occuring and/or b) if your host is able to action one of the other options listed in the article linked above?