Terminal
Terminal/Skill
Diagnoses DNS resolution inside an AWS VPC from a live instance, and checks whether a proposed Route 53 or Resolver change would break names.
By Amazon Web Services
Works with
npx skills add aws/tools-for-devops-agent --skill aws-vpc-dns-investigationUse the tools on the connected aws-vpc-dns-diagnostics MCP server.
Before calling any tool, determine which mode applies:
If the request is ambiguous, ask the operator to clarify. Do not default to Mode A when the input lacks an instance ID, and do not default to Mode B when the operator describes a live symptom.
Regardless of mode, call get_sop with slug A-critical-safety-rules and
follow every rule it contains. These are non-negotiable constraints on how you
interpret results, handle opaque constructs, and report findings.
account_id, region, instance_id, and the failing DNS name.
dns_probe_context — establishes VPC-attribute preconditions: enableDnsSupport,
enableDnsHostnames, address family, DHCP option set. A resolution result means
nothing until you know whether the VPC resolver is answering.dns_probe_compare — runs the allowlisted probe set inside the instance via
SSM. Returns each resolver's answer and the resolver's own identity from
hostname.bind. The VPC DHCP resolver is auto-added for comparison.get_sop — load the pattern runbook matching the observed signature
(see trap-to-SOP mapping below).enableDnsSupport is false: load A-resolver-disabled-precondition. The
VPC resolver is intentionally dark and every probe failure follows from that./etc/resolv.conf (from the probe output) against the
DHCP option set. A mismatch means the instance is not using the VPC-intended
resolver.A-name-category-classification), not by
whether resolvers agree. Two resolvers returning the same wrong answer is still
a failure.| Observed signature | SOP slug |
|---|---|
| Custom resolver answers differently from VPC .2 | A-custom-resolver-divergence |
| FORWARD rule and PHZ both match the name | A-forward-vs-phz-precedence-collision |
| A record works, AAAA fails (or vice versa) | A-address-family-divergence |
| enableDnsSupport is false | A-resolver-disabled-precondition |
| General live comparison procedure | A-mode-a-live-resolver-comparison |
Label every finding as Observed (ground truth from the probe). State which resolver answered and what it returned. When Mode A and Mode B produce different conclusions for the same name, Mode A wins because it is ground truth from inside the subnet.
account_id, region, vpc_id, and a change descriptor (structured dict with type
and type-specific fields). No instance required.
dns_simulate_effective_config — returns the VPC's effective DNS config: the
union of directly attached resources and anything inherited through an
associated Route 53 Profile, each construct tagged by source.dns_simulate_change — applies the proposed change symbolically and returns a
per-name impact report (before/after, delta, traps, severity, volume).get_sop — load runbooks for any traps reported in the impact table
(see trap-to-SOP mapping below).volumes (from Resolver Query Logs), names are ranked
by traffic. This is enrichment; absence does not invalidate the simulation.| Trap label in impact report | SOP slug |
|---|---|
| VPCE-shadow-NXDOMAIN | B-vpce-shadow-nxdomain |
| broad-FORWARD-sweep | B-broad-forward-sweep |
| flag-AND-mismatch | B-flag-and-mismatch |
| DNS-Firewall-block | B-dns-firewall-block |
| profile-union-shift | B-profile-propagation-timing |
| General pre-change procedure | B-mode-b-pre-change-validation |
Label every finding as Predicted (symbolic, not ground truth). State the candidate-set size, its source (API-derived or operator-supplied), and that names outside this set were not evaluated. Include the propagation timing caveat for Profile changes.
Call get_sop with slug C-cross-account-opaque-constructs when the effective
config or impact report contains opaque markers. Cross-account constructs shared
via RAM or a Route 53 Profile may be enumerable but their contents are not
readable from the consumer account. Report them as "present but unknown content"
rather than treating them as absent or inferring past them.
Call get_sop with slug C-limitations-and-boundaries and state the relevant
boundaries to the operator. Key constraints:
Every response produced by this skill must include:
Requires the aws-vpc-dns-diagnostics MCP server registered in the Agent Space
with its tools allowlisted. The server is at mcp/aws-vpc-dns-diagnostics-mcp/.
If the server is not registered or SSM is unreachable, report that as the blocker
rather than guessing at the resolution path.