PowerShell を使用して DNS ゾーンとレコードを作成および管理する方法

$NewDNS. RecordData. IPv4Address = [System. Net. IPAddress]::parse('192.168.100.133')

Set-DnsServerResourceRecord -NewInputObject $NewDNS -OldInputObject $OldDNS -ZoneName woshub.com -ComputerName dc01

And make sure it’s updated:

Get-DnsServerResourceRecord -Name ber-rds1 -ZoneName woshub.com

Want to list all CNAME records to troubleshoot? Just add -RRType CNAME:

Get-DnsServerResourceRecord -ComputerName DC01 -ZoneName woshub.com -RRType CNAME

Or filter records with specific names or patterns using:

Get-DnsServerResourceRecord -ZoneName woshub.com -RRType A | Where-Object HostName -like "*rds*"

Removing records? Easier than you think. For example, delete a CNAME with:

Remove-DnsServerResourceRecord -ZoneName woshub.local -RRType CName -Name Ber-RDSFarm

Or an A record:

Remove-DnsServerResourceRecord -ZoneName woshub.local -RRType A -Name ber-rds1 –Force

Same goes for PTR records in reverse zones.

Bulk Creating Records from CSV Files

Now, here’s the thing — doing records one by one sucks. Instead, if you have a CSV with all your hostnames and IPs, automate the whole process. Create a text file, say NewDnsRecords.txt, with this format:

HostName, IPAddress host1, 192.168.100.10 host2, 192.168.100.11 

And run this PowerShell snippet:

Import-Csv "C:\PS\NewDnsRecords.txt" | %{ Add-DnsServerResourceRecordA -ZoneName woshub.com -Name $_."HostName" -IPv4Address $_."IPAddress" }

If you want PTR records for reverse DNS, add –CreatePtr and modify the script accordingly, or process a file with the hostname, octet, and zone info. For example, a CSV like:

octet, hostName, zoneName 102, ber-rds2.woshub.com, 100.168.192.in-addr.arpa 103, ber-rds3.woshub.com, 100.168.192.in-addr.arpa 

And run a similar import script:

Import-Csv "C:\PS\NewDnsPTRRecords.txt" | %{ Add-DNSServerResourceRecordPTR -ZoneName $_."zoneName" -Name $_."octet" -PTRDomainName $_."hostName" }

Always double-check your DNS through the DNS Manager console (dnsmgmt.msc) after bulk changes — nothing worse than missing records or typos.

Wrap-up

Handling DNS with PowerShell isn’t rocket science, but it’s easy to get overwhelmed when you’re doing it manually or in big batches. These commands are a good starting point, and once you get why they work, automating DNS tasks becomes way less stressful. Just keep testing in a lab environment if possible, and remember — always backup your DNS zones before making major changes, in case something goes sideways. Overall, scripting DNS management with PowerShell can seriously streamline your workflow, especially if you manage lots of zones or records regularly.

Summary

• Make sure the DNSServer module is installed and imported.
• Use Get-DnsServerZone and Add-DnsServerPrimaryZone to oversee and create zones.
• Add or update DNS records with commands like Add-DnsServerResourceRecordA or Set-DnsServerResourceRecord.
• Bulk operations? Just import from CSV and run the script.
• Always verify your changes in DNS Manager or with Get-DnsServerResourceRecord.

Fingers crossed this helps speed up your DNS workflows — because Windows DNS can be a real stubborn beast sometimes, but PowerShell makes it a lot more manageable.