DNS issues after implementing GeoBlock policy.

MKarasev — Thu, 28 May 2020 13:38:26 GMT

Hey guys, wanted to see if I can can get any input on this here - had to Geoblock one of the countries for inbound/outbound traffic completely. Everything was fine until I found out that one of the employees started having issues with email delivery to the certain customer - "domain of sender address xxxx@mydomain.com does not resolve customer.email@customerdomain.com". Turns out mail servers of this certain customer (as well as other server infrastructure) located in that Geoblocked zone. Tried to identify range of their public addresses and allow inbound/outbound dns and smtp applications from my mail server and on-prem dns servers (just in case).

Issue still exists. No problems/issues with incoming emails from customer.email@customerdomain.com.

Will appreciate any help/suggestions.

Thanks.

Re: DNS issues after implementing GeoBlock policy.

mivaldi — Thu, 28 May 2020 16:18:39 GMT

Query your traffic logs for denied traffic where your SMTP server is the source address.

Re: DNS issues after implementing GeoBlock policy.

MKarasev — Tue, 02 Jun 2020 14:47:08 GMT

Issue resolved, problem resided in the policy with the wrong DMZ zone assigned.

topic DNS issues after implementing GeoBlock policy. in Advanced Threat Prevention Discussions

DNS issues after implementing GeoBlock policy.

Re: DNS issues after implementing GeoBlock policy.

Re: DNS issues after implementing GeoBlock policy.