feat: add support for dns monitor documentation #54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pmallol
reviewed
Oct 14, 2025
images/dns-request.png
Outdated
There was a problem hiding this comment.
This UI has changed a tiny bit (inputs fit 100% width of section )
Co-authored-by: Paula Mallol <[email protected]>
Co-authored-by: Paula Mallol <[email protected]>
Co-authored-by: Paula Mallol <[email protected]>
Co-authored-by: Paula Mallol <[email protected]>
Automatically fetched from https://api.checklyhq.com/swagger.json Updated on 2025-10-15 02:33:42 UTC
pmallol
approved these changes
Oct 15, 2025
| Current limitations: | ||
|
|
||
| - **Private locations**: DNS monitors do not currently support private locations. You can only run DNS monitors from Checkly's global public locations. | ||
| - **Protocol**: DNS queries use UDP by default with automatic TCP fallback. You can pin to UDP-only or TCP-only if needed. |
There was a problem hiding this comment.
nit: I don't think that is the case, we explicitly set a protocol which is used for the DNS query. 🤔
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Given that DNS monitors are still in development, these docs require a final review and update once the feature has been finalized. A few notes on current gaps:
The section "Troubleshooting Common Issues" is currently AI generated. Would be great to get someone with DNS expertise to provide feedback on whether these are helpful examples.
Any copy related to JSON responses and JSON path assertions was a bit of a guessing game on my end, the snippets and assertion examples would need to be reviewed.
Anything else worth mentioning in the dev docs? e.g. any caching or lookup behavior that might be worth calling out for more technical folks?