Routines
Check the DNS records you meant to have
dns-record-check
Put the records you expect next to a public lookup. Query only. Do not edit.
for Grok Bot · unofficial, not affiliated with xAI
CNPS0.1.02026-11-18New
Paste this into Grok Bot and say: create this routine.
Create this routine: Check the DNS records you meant to have
Trigger: When you update dns/expected.md, or once a week for a public lookup. Query only. Do not edit records.
What to do:
1. Reads the name, type, and value you expect.
2. Looks up what is public now.
3. Lists missing records, extra public records, and values that differ.
How:
1. Write the records you intend to be public in dns/expected.md. Do not write the registrar password.
2. Query public DNS for each name and type. Do not install an app named Public DNS lookup. The docs do not name one. Do not sign into a registrar.
3. Run it once by hand and compare with the DNS host's screen.
4. You make the change yourself. This routine only writes a report.
Rules you can keep:
Read dns/expected.md. Each line has a name, a type (A, AAAA, CNAME, MX, TXT), and the expected value.
Look up each one in public DNS. On failure, write the failure. Do not fill the value from memory.
Output three sections: missing, extra public records, values that differ.
Write outputs/dns.md.
Do not log into the registrar. Do not create, delete, or edit a record.
Do not:
- Do not put an API token or a registrar password in the expected file.
- Do not reuse the previous value when a lookup fails.
- Do not sign into a registrar, and do not create, edit, or delete DNS records.
Paste this into Grok Bot and say: create this routine.What it does
- Reads the name, type, and value you expect.
- Looks up what is public now.
- Lists missing records, extra public records, and values that differ.
Who it is for
People who changed domain, mail, or verification records and want to see the public result.
How to put it in Grok Bot
- Write the records you intend to be public in dns/expected.md. Do not write the registrar password.
- Query public DNS for each name and type. Do not install an app named Public DNS lookup. The docs do not name one. Do not sign into a registrar.
- Run it once by hand and compare with the DNS host's screen.
- You make the change yourself. This routine only writes a report.
Example
Routine snippet
Read dns/expected.md. Each line has a name, a type (A, AAAA, CNAME, MX, TXT), and the expected value.
Look up each one in public DNS. On failure, write the failure. Do not fill the value from memory.
Output three sections: missing, extra public records, values that differ.
Write outputs/dns.md.
Do not log into the registrar. Do not create, delete, or edit a record.Connectors it needs
No connector.
Safety and permissions
- Do not put an API token or a registrar password in the expected file.
- Do not reuse the previous value when a lookup fails.
- Do not sign into a registrar, and do not create, edit, or delete DNS records.
Risk: Low
Questions
I just changed it and the lookup is still old.
Public resolvers lag. Write the lookup time in the report. Do not loop the routine to force a refresh.
Does MX explain a site that will not load?
MX is for mail. For a site that will not load, use Site uptime and certificate expiry and the A or AAAA record.
0.1.0
2026-11-18
First published text. Public lookup only.