NXFilter not in sync with upstream DNS server

[avidflyer]

I'm noticing that DNS updates I am making on my primary DNS server yesterda have not gotten picked up by NXFilter yet.
How can I force NXFilter to reload the zone from the authoritative server, and how can I ensure that it is querying/listening for changes to the authoratative server?
Right now I have NXFilter only pointing to one primary DNS server, and then am using it as default resolver for all my network assets. So, when changes I make don't propogate in a timely manner it's a bad thing.
The record that is not being updated from the primary upstream DNS server has a 3600 second TTL, so it should have been updated on NXFilter by now.
I have Use Persistent Cache and Use Negative Cache checkes, and have a 0 value in the Minimum Cache TTL, which says that means "bypass", which I assume means use the TTL value from the primary server.

Thanks.

[support200]

There are three types of DNS response caches in NxFilter designed to reduce traffic and workload.

1. Normal Cache
The Normal Cache stores responses from the upstream server until their TTL expires. When a cached record expires, NxFilter refreshes it by querying the upstream server again.

2. Negative Cache
The Negative Cache stores negative responses from the upstream server. It keeps Server Failure or Non-existent Domain responses for up to 15 minutes. It is unrelated to the behavior being discussed here.

3. Persistent Cache
The Persistent Cache is used when there is a network failure. However, there is one exception. When a Normal Cache entry expires, NxFilter returns the Persistent Cache answer once and then refreshes the Normal Cache. This is for providing a fast response without any delay.

So, if you are the only one querying a domain, you will get a temporary 60 TTL with the old answer. If there are other users querying it, they will receive the correct, newly refreshed answer.

You can manipulate the caches with 'cachecon.sh' script. https://tutorial.nxfilter.org/doc/en...hp#clear-cache

When viewing the cache state with the script, you need to send some DNS queries first in order to trigger TTL updates. Otherwise, you won't see any changes.

[avidflyer]

Thanks, support200

[support200]

Sorry. There's one thing wrong. For temporary cache, you get 60 seconds TTL not another 3600 TTL.