Skip to content

Hardcoded 300s TTL for negative responses, should use SOA.MINIMUM #114

@poyrazK

Description

@poyrazK

Why is this an issue?

In internal/dns/server/server.go:1144-1149, NXDOMAIN responses default to 300s TTL instead of using SOA.MINIMUM field per RFC 2308. Many SOA records set MINIMUM to 3600.

What is causing it?

var ttl uint32 = 300  // Should be SOA.MINIMUM or higher

How can it be solved?

Parse and use SOA.MINIMUM field for negative caching TTL.

Category

  • Small
  • Medium
  • Large

Severity

  • Low
  • Medium
  • High
  • Critical

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions