feat: add Add/Remove/Get-PiHoleDnsRecord

[mikemadeja]

Summary

• Adds Add-PiHoleDnsRecord / Remove-PiHoleDnsRecord / Get-PiHoleDnsRecord as DNS-specific convenience wrappers for managing Pi-hole's local DNS records
• This capability already existed generically via Add-PiHoleConfigArrayItem/Remove-PiHoleConfigArrayItem/Get-PiHoleConfig on dns/hosts and dns/cnameRecords - these just make it discoverable with typed, DNS-specific parameters instead of requiring callers to know Pi-hole's raw value format:

  Add-PiHoleDnsRecord -PiHoleServer $Server -Password $Password -Type A -Hostname "test.local" -IPv4Address "192.168.1.1"
  Add-PiHoleDnsRecord -PiHoleServer $Server -Password $Password -Type AAAA -Hostname "test.local" -IPv6Address "::1"
  Add-PiHoleDnsRecord -PiHoleServer $Server -Password $Password -Type CNAME -Hostname "alias.local" -Target "test.local" -Ttl 300
  
  Get-PiHoleDnsRecord -PiHoleServer $Server -Password $Password -Hostname "test.local" |
      Remove-PiHoleDnsRecord -PiHoleServer $Server -Password $Password

• Add/Remove are thin wrappers that call the existing config-array functions internally rather than duplicating their auth/HTTP/error-handling logic. Get parses .Dns.Hosts/.Dns.CnameRecords into the same typed object shape (Type/Hostname/IPv4Address/IPv6Address/Target/Ttl), filterable by -Type/-Hostname
• -IPv4Address/-IPv6Address are validated against the real .NET address family (so passing an IPv6 address to -IPv4Address or vice versa fails fast with a clear error, before any network call)
• Remove-PiHoleDnsRecord implements its own -WhatIf/-Confirm via ShouldProcess, passing -Confirm:$false through to the inner call to avoid double-prompting
• Remove-PiHoleDnsRecord accepts Get-PiHoleDnsRecord's output via ValueFromPipelineByPropertyName, including removing several matched records in one pipeline call - the first use of pipeline input anywhere in this module

Test plan

• Manually created and removed one of each record type (A, AAAA, CNAME-with-TTL) against a live server, confirmed each via Get-PiHoleConfig/Get-PiHoleDnsRecord, confirmed clean removal
• Manually verified the full Get-PiHoleDnsRecord | Remove-PiHoleDnsRecord pipeline, including removing multiple records (AAAA + CNAME) in one pipeline call
• Integration tests pass against a live server (25/25 in the DnsControl folder, including the 4 pre-existing Set-PiHoleDnsBlocking/Get-PiHoleDnsBlockingStatus tests - no regressions): create/verify for all 3 types, filtering by -Type/-Hostname, RawOutput, the pipeline chain (single and multi-record), error paths (missing required param per type, invalid IPv4 format), -WhatIf performs no request, bad password
• PSScriptAnalyzer clean
• Full non-integration unit suite passes (18/18), including the module-export-integrity test confirming all three new functions are correctly exported
• README.md / docs/EXAMPLES.md / manifest FunctionsToExport all regenerated

🤖 Generated with Claude Code

[sonarqubecloud]

❌ The last analysis has failed.

See analysis details on SonarQube Cloud