ipam-dns-audit

Automate IPAM and DNS reconciliation to surface inconsistencies and conflicts.

Updated Mar 15, 2026

Search Tags:#audit #reconciliation #network #dns #ipam #subnet #ip-conflict

Ready to run

npx skills add https://github.com/vahagn-madatyan/netsec-skills-suite --skill ipam-dns-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ipam-dns-audit
Source: https://github.com/vahagn-madatyan/netsec-skills-suite/tree/main/skills/ipam-dns-audit
Command: npx skills add https://github.com/vahagn-madatyan/netsec-skills-suite --skill ipam-dns-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

IPAM and DNS reconciliation audits identify gaps between recorded IP allocations and live network state, surfacing inconsistencies, orphaned records, and potential conflicts that undermine reliability.

Core Features & Use Cases

IPAM inventory analysis to map allocations, utilization, and gaps
Live subnet discovery with DNS/DHCP data validation to ensure current state accuracy
DNS record audit to detect forward/reverse mismatches, stale entries, and delegation issues
Reconciliation reporting with health scoring and remediation guidance for pre-migration and ongoing governance

Quick Start

Run the IPAM/DNS reconciliation workflow across target subnets and zones to begin auditing.

Frequently Asked Questions about ipam-dns-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I reconcile IPAM and DNS records to find inconsistencies?▼

IPAM and DNS reconciliation automates the comparison of recorded IP allocations against live network state to surface orphaned records, mismatches, and conflicts. It validates subnet allocations and DNS entries to ensure current state accuracy.

What is IPAM reconciliation and when do I need it?▼

IPAM reconciliation is the process of identifying gaps between recorded IP allocations and live network state. You need it during subnet audits, DHCP scope health assessments, and pre-migration planning to catch stale entries and potential conflicts.

How do I detect forward and reverse DNS mismatches across enterprise subnets?▼

Detecting forward and reverse DNS mismatches requires validating forward and reverse DNS zones against live ARP and DHCP data. The audit checks for delegation issues and stale entries to ensure DNS hygiene across enterprise networks.

Can I use this DNS audit workflow for pre-migration network planning?▼

Yes, DNS audit workflows support pre-migration planning by generating structured reconciliation reports with health scoring and remediation guidance. This ensures accurate network state before migrating subnets or consolidating zones.

What's the best way to assess DHCP scope health and IP utilization across subnets?▼

Assessing DHCP scope health involves extracting IPAM prefixes and validating live ARP and DHCP data to map allocations, utilization, and gaps. This surfaces orphaned records and IP conflicts that undermine network reliability.

Why does my subnet show IP conflicts when IPAM records appear accurate?▼

IP conflicts occur when IPAM records diverge from live network state due to stale entries or unrecorded allocations. Reconciliation audits surface these inconsistencies by comparing recorded prefixes against live ARP and DHCP data.