Parental Control restrictions keep reappearing after being disabled – Logs confirm “Blocked by Social Media / Facebook".

I believe I am experiencing a bug with NextDNS Parental Control.

I previously used Parental Control to block Social Media and individual services such as Facebook, Instagram, Pinterest, etc.

I have now disabled/removed these restrictions. The NextDNS dashboard clearly shows these services/categories as unblocked.

However, NextDNS starts blocking them again even though I have not re-enabled the restrictions.

I checked the NextDNS Logs while reproducing the problem. The blocked queries specifically show reasons such as:

- Blocked by Social Media
- Blocked by Facebook

The same thing happens with Instagram, Pinterest and other services that I had previously blocked through Parental Control.

Strange timing/behavior

If I enable the restrictions again and then disable them:

1. The websites eventually start working again.
2. There appears to be different behavior between devices using DoT/Android Private DNS and browsers using NextDNS DoH.
3. After approximately 6–7 hours, the websites can become blocked again on DoT devices as well.
4. I check the NextDNS dashboard again and the Parental Control restrictions are still disabled.
5. Nevertheless, the Logs explicitly identify Social Media/Facebook/etc. parental controls as the blocking reason.

This can persist even days after I originally disabled the restrictions.

This does not look like normal client-side DNS caching because the websites first become accessible and then become blocked again several hours later without any configuration change from me.

I have also verified that the restrictions shown in my NextDNS configuration remain disabled when the problem occurs.

Could this be an issue with an old/stale version of the configuration being applied by some NextDNS resolver/edge servers, or some other configuration synchronization issue?

Please let me know what diagnostic information would be useful to identify which configuration state the resolver is applying.