Fix ednscachetimeout range/default in dnscmd docs

[adam (sa1181405)]

The dnscmd documentation currently lists an incorrect valid range (and default) for ednscachetimeout:

Currently documented: 3600-15724800 seconds (default 604800 / one week)

In practice, dnscmd enforces 10-86400 seconds (default 900 / 15 minutes)

Values > 86400 fail with DNS_ERROR_DWORD_VALUE_TOO_LARGE
Values < 10 fail with DNS_ERROR_DWORD_VALUE_TOO_SMALL

This PR updates the dnscmd docs to match the authoritative DNS Server Integer Properties documentation:

dnscmd docs: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/dnscmd

DNS Server Integer Properties: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dnsp/8903e50a-9183-4a7d-9640-53f6f5a91481

[prmerger-automator]

adam (@sa1181405) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit b2a38f6:

✅ Validation status: passed

File	Status	Preview URL	Details
WindowsServerDocs/administration/windows-commands/dnscmd.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull request overview

This PR corrects the documented valid range and default value for the ednscachetimeout parameter in the dnscmd documentation to match the actual implementation in the DNS Server.

Changes:

• Updated the valid range from 3600-15724800 seconds to 10-86400 seconds
• Corrected the default value from 604800 seconds (one week) to 900 seconds (15 minutes)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Tracey Torble (ttorble)]

#assign: Robin Harwood (@robinharwood), dknappettmsft

Robin Harwood (@robinharwood) dknappettmsft

Can you review the proposed changes?

#label:"aq-pr-triaged"

@MicrosoftDocs/public-repo-pr-review-team

[prmerger-automator]

Users robinharwood are already assigned.