{
  "context": "Evaluates how well the solution routes socket-based hostname lookups through dnspython by configuring a custom Resolver, installing the library's system override, and restoring the original resolver safely after use.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Resolver setup",
      "description": "Constructs a dns.resolver.Resolver (or equivalent factory) with the provided nameservers and applies timeout/search parameters via the resolver's attributes instead of manual socket stubs.",
      "max_score": 20
    },
    {
      "name": "Override activation",
      "description": "Calls dns.resolver.override_system_resolver with the configured resolver so socket.getaddrinfo (and related calls) are routed through dnspython before performing lookups.",
      "max_score": 25
    },
    {
      "name": "Default resolver control",
      "description": "Uses dns.resolver.get_default_resolver and dns.resolver.set_default_resolver to manage the resolver that the override installs, preserving and restoring any pre-existing default when swapping in the custom one.",
      "max_score": 15
    },
    {
      "name": "Safe restoration",
      "description": "Ensures dns.resolver.restore_system_resolver is invoked in __exit__/finally paths so the original socket resolver is reinstated even when exceptions occur or when nested overrides unwind.",
      "max_score": 25
    },
    {
      "name": "Active status",
      "description": "Reports active override state based on whether dnspython's override is currently installed (e.g., tracking calls to override_system_resolver/restore_system_resolver) rather than unrelated flags, correctly handling nested activation counts.",
      "max_score": 15
    }
  ]
}