Own DNS incidents and gaps
Connect
SPIRITT
Control DMake DNS policy deliberate
Operate profiles with evidence
Manage Control D profiles, DNS endpoints and scoped rules, then use available analytics to verify what changed. Create or clone profiles and configure filters and rules for the intended device group.
What you can do with Control D.
Profiles that match the purpose
Create or clone profiles and configure filters and rules for the intended device group.
Endpoints with clear ownership
Provision DNS endpoints and maintain their profile assignments with an explicit client handover.
Changes grounded in traffic
Use enabled analytics and query logs to investigate filtering behavior and follow up on exceptions.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for profiles that match the purpose and give it your operating priorities.
02
Connect Control D
Connect your Control D account and choose the records and actions this workspace may use. Name profiles and devices; distinguish resolver setup from verified client traffic.
03
Delegate an outcome
Ask SPIRITT to build a dns operations desk. It carries the work through and checks the result.
Hand over a mission.
Choose a mission. Make it yours.
Put Control D to work.
Operate profiles with evidence
Questions
Control D, with SPIRITT.
01Can it provision DNS endpoints?+
Yes. It can create endpoints using an existing profile and return resolver URLs and addresses. Physical client configuration remains a distinct setup step.
02Can it change filters and custom rules?+
Yes. It supports native and external filter state plus block, bypass, spoof and redirect rules within a selected profile.
03Are traffic logs always available?+
No. Analytics must be enabled for relevant log data. SPIRITT treats missing logs as unavailable evidence, not proof of no activity.
04Can it set recurring schedules?+
It can create, retrieve and update profile schedules for the approved enforcement windows.
05What happens if a device is deleted?+
Deleting an endpoint breaks DNS resolution on clients configured with its unique resolvers. These missions avoid endpoint deletion unless an exact migration and removal is separately approved.
06Can it remove unused profiles?+
Yes, but the profile must be orphaned. SPIRITT checks device assignments before an approved profile deletion.