This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DNS - DNSSEC vs. sharepoint.com over Google Public DNS leads to "Host not found" error

Hello,

we have configured the UTM (9.355-1) DNS according to "DNS best practice" by Bob Alfson and KB https://www.sophos.com/de-de/support/knowledgebase/120283.aspx.

The DNSSEC option in the UTM DNS Proxy/Forwarder is on and did not give us problems since 2013.

But now, something strange happens:

If we try to access "sharepoint.com" or "companyname-my.sharepoint.com" we get a "Host not found" error as long as DNSSEC is activated.

I have tested this on two different Environments over different ISPs and It seems like it does only affect this domain.

We'd like to keep the option enabled, because we still have some older ISP-Routers in front of the UTM for failover reasons and cache poisoning is not out of question.

Maybe someone could test this?

Or is the DNSSEC implementation of the UTM DNS Proxy worthless as it used to be with some typical older router Firmwares?

Best Regards,

HP



This thread was automatically locked due to age.
Parents Reply Children
No Data