An agent on the resolver, the core in the cloud
ArgusDNS is delivered as a service: list preparation and signing, the panel and reports run in the cloud. In the ISP network there is only the agent on the resolver.
Three parts
What overrides what
The resolver applies the first list in which the domain is found, so the order decides what overrides what.
- 1Blocking by lawThe highest priority: these are decisions of state bodies, and nothing overrides them.
- 2Own blocksDomains you block yourself.
- 3Organization exceptionsThey only cancel hits of the protection levels that come below.
- 4NCSCC phishing filterIf it is on.
- 5Protection levelThe active level: L1, L2 or L3.
Where the phishing filter comes from
The core pulls the NCSCC list, keeps only domain names and substitutes its own action, signs it and delivers it to servers by the same path as blocking by law.
So a resolver does not need its own copy of the NCSCC zone or to track the addresses of its servers.
What the agent changes in your resolver
The agent adds one file to unbound and shows the diff before applying it. Your main config is not rewritten.
A restart may be needed only for the first application; after that lists and config update with no restarts.
No changes to unbound
The agent takes queries from dnstap if it is there, or captures packets on the interfaces. So statistics work on FreeBSD, where there is no dnstap, and when the resolver is behind NAT or listens on loopback.
The core receives only per-minute aggregates: counters, top lists, hits. unbound's own counters are shown on a separate server tab.
Encrypted listeners under watch
If the resolver serves DNS-over-TLS or DNS-over-HTTPS, the agent sees the certificates and warns ahead of time that one is about to expire. It also reports when a certificate has been renewed on disk but the port still serves the old one.
The server card shows queries and errors for every listener.