--- name: dns-record-analyzer-46a845791975 description: >- Audits and troubleshoots DNS records for domains including A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, CAA, and NS records. Use when someone needs to verify DNS configuration, debug DNS propagation issues, check email authentication records, or audit domain security. Trigger words: DNS records, dig, nslookup, SPF, DKIM, DMARC, MX records, DNS propagation, nameservers, CAA, domain configuration. license: Apache-2.0 compatibility: "Requires dig or nslookup (available on most systems)" metadata: author: terminal-skills version: "1.1.0" category: devops tags: "dns, domain, email-authentication, infrastructure" --- # DNS Record Analyzer ## Overview This skill queries and analyzes DNS records for domains, checking for correctness, security best practices, and common misconfigurations. It covers standard records (A, CNAME, MX) and email authentication records (SPF, DKIM, DMARC) with specific validation rules for each. ## Instructions ### Step 1: Query All Record Types ```bash DOMAIN="northwind-labs.dev" # Core records dig +short A $DOMAIN dig +short AAAA $DOMAIN dig +short CNAME $DOMAIN dig +short MX $DOMAIN dig +short NS $DOMAIN dig +short TXT $DOMAIN # Email authentication dig +short TXT $DOMAIN | grep "v=spf1" dig +short TXT _dmarc.$DOMAIN dig +short TXT default._domainkey.$DOMAIN # Security and transport dig +short CAA $DOMAIN dig +short SOA $DOMAIN dig +short DS $DOMAIN # DNSSEC delegation signer (empty = not signed) dig +short TXT _mta-sts.$DOMAIN # MTA-STS policy pointer dig +short TXT _smtp._tls.$DOMAIN # TLS-RPT reporting # Compare resolvers, or ask an authoritative server directly dig +short TXT $DOMAIN @8.8.8.8 dig +short TXT $DOMAIN @1.1.1.1 dig +nssearch $DOMAIN # SOA serial on every authoritative server ``` `nslookup -type=TXT $DOMAIN` works where `dig` is missing (Windows). Long TXT values come back as several quoted chunks; join them before judging the record. ### Step 2: Validate SPF Check these rules: - Starts with `v=spf1` - Ends with `-all` (hardfail) or `~all` (softfail) — recommend `-all` - Exactly one SPF record per name (two `v=spf1` TXT records = PermError) - Total DNS lookups ≤ 10 (count `include:`, `a`, `mx`, `ptr`, `exists:` and `redirect=`, including nested ones; `ip4:`, `ip6:` and `all` are free), and no more than 2 void lookups (names that return nothing) - No `ptr` mechanism (deprecated) - No duplicate mechanisms - All referenced includes resolve (no NXDOMAIN) - No `+all` (this allows anyone to send as your domain) ### Step 3: Validate DKIM For each sending service, check the expected selector: - Record exists and is a valid RSA public key - Key is ≥ 1024 bits (recommend 2048; an empty `p=` means the key was revoked) - Common selectors: `google` (Google Workspace), `selector1`/`selector2` (Microsoft 365), `s1`/`s2` (SendGrid), `k1` (Mailchimp); many providers use CNAMEs, so ask `dig +short CNAME` as well as TXT - `t=y` (testing mode) should NOT be present in production ### Step 4: Validate DMARC ``` v=DMARC1; p=reject; rua=mailto:dmarc-reports@northwind-labs.dev; adkim=s; aspf=r ``` Check: - `p=` is `quarantine` or `reject` (not `none` in production) - `rua=` is present (aggregate reports); if it points to another domain, that domain must publish `northwind-labs.dev._report._dmarc.reports-vendor.net` (your domain, then the vendor domain) authorising it - `pct` below 100 only during a staged rollout (`none` → `quarantine` → `reject`); the newer DMARC revision replaces it with `t=`, so do not rely on it long-term - `ruf=` forensic reports are rarely sent by large providers; do not count on them - Subdomain policy `sp=` if subdomains send email - Alignment: DMARC passes only if SPF or DKIM passes *and* the domain matches the From header - Mailbox providers (Google, Yahoo, and since May 2025 Microsoft Outlook.com) require SPF, DKIM and DMARC from bulk senders (5,000+ messages a day) ### Step 5: Check MX Records - MX records exist and resolve to valid hostnames - Priority values are reasonable (lower = higher priority) - No MX pointing to IP addresses or to a CNAME (must be hostnames with A/AAAA); a domain that sends but never receives mail should publish a null MX (`0 .`) - Hostnames have valid A/AAAA records ### Step 6: Produce Audit Report Categorize findings as: - ✅ Correct and secure - ⚠ Works but suboptimal (with recommendation) - ❌ Broken or insecure (with exact fix) ## Examples ### Example 1: Full Domain Audit **User prompt:** ``` Audit all DNS records for myapp.io ``` **Agent output:** ``` DNS Audit — myapp.io ──────────────────── A Records: ✅ 104.21.45.12 (Cloudflare) ✅ 172.67.182.88 (Cloudflare) AAAA Records: ✅ 2606:4700:3030::6815:2d0c ✅ 2606:4700:3037::ac43:b658 MX Records: ✅ 1 aspmx.l.google.com ✅ 5 alt1.aspmx.l.google.com ✅ 10 alt2.aspmx.l.google.com (Google also accepts the single record "1 smtp.google.com") NS Records: ✅ cody.ns.cloudflare.com ✅ krystal.ns.cloudflare.com SPF: v=spf1 include:_spf.google.com include:sendgrid.net ~all ✅ Google Workspace authorized ✅ SendGrid authorized ⚠ Using ~all (softfail) — recommend changing to -all ✅ Lookup count: 5 of 10 DKIM: ✅ google._domainkey → valid 2048-bit RSA ❌ s1._domainkey → NXDOMAIN (SendGrid DKIM not configured!) Fix: Add CNAME s1._domainkey.myapp.io → s1.domainkey.u1234.wl.sendgrid.net DMARC: v=DMARC1; p=none; rua=mailto:admin@myapp.io ❌ p=none provides no protection Fix: Change to p=quarantine (after fixing DKIM above) CAA: ❌ No CAA records — any CA can issue certificates for your domain Fix: Add CAA 0 issue "letsencrypt.org" (and any other CAs you use) Summary: 2 critical fixes, 2 recommendations ``` ### Example 2: SPF Lookup Count **User prompt:** ``` Are we over the SPF lookup limit? We use Google, SendGrid, Mailchimp, Zendesk, and HubSpot. ``` **Agent output:** ``` SPF Lookup Analysis — northwind-labs.dev Current record: v=spf1 include:_spf.google.com include:sendgrid.net include:servers.mcsv.net include:mail.zendesk.com include:spf.hubspot.com -all Lookup breakdown (each include counts itself plus everything nested in it, as resolved today with dig +short TXT ): include:_spf.google.com → 4 include:sendgrid.net → 1 include:servers.mcsv.net → 2 include:mail.zendesk.com → 3 include:spf.hubspot.com → 2 ───────────────────────────────────── Total: 12 lookups ❌ OVER LIMIT (max 10) Impact: a receiver that counts more than 10 lookups returns PermError, and SPF fails for ALL mail from this domain, not only for the last services. Fix options: 1. Remove services that no longer send mail 2. Send from a subdomain per service (e.g. help.northwind-labs.dev for Zendesk) with its own SPF record 3. SPF flattening (replace includes with ip4:/ip6: ranges); needs automatic refresh because providers change their IPs ``` ## Guidelines - **Always check recursively** — an SPF `include:` may itself include others; count ALL lookups - **DKIM selectors vary by provider** — check provider documentation for the correct selector name - **TTL matters for changes** — note the current TTL when recommending DNS changes; high TTL means slow propagation - **Test from multiple resolvers** — caches differ; compare `@8.8.8.8` and `@1.1.1.1`, and ask the authoritative servers (`dig +short NS`, then `dig @ns-server`) for the truth - **Do not change records blindly** — SPF/DMARC edits affect real mail delivery; start DMARC at `p=none` with `rua=` and only tighten after reports look clean - **CAA records are underused** — always recommend them to prevent unauthorized certificate issuance - **Don't forget subdomains** — `www.northwind-labs.dev` and `mail.northwind-labs.dev` may have different records that need auditing --- Source attribution: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/dns-record-analyzer/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2025 Terminal Skills Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/dns-record-analyzer/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Customer Support, Operations Roles: DevOps / SRE, Technical Support, IT Operations Specialties: DevOps Tools: Dig, Nslookup Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: 6021df0e65b633ca21f85d048de192f39341e362be6bcb4eab1de9ef77a979fd