Add scripts/Powershell/General Purpose/Remotely Change DNS Records.md
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 6s
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 6s
This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
## Purpose
|
||||
You may find that for one reason or another, you need to change DNS records of remote windows devices and cannot login via RDP or via console, yet somehow WinRM continues to work. In these scenarios, you can use the following commands to identify the network adapter, change its DNS servers, and verify the settings afterwards.
|
||||
|
||||
!!! info "Run as Domain Admin"
|
||||
You need to run the following commands within the context of a powershell session running as a domain admin, otherwise the `Invoke-Command` commands will fail to execute.
|
||||
|
||||
```powershell
|
||||
# Hostname of the Device
|
||||
$DEVICE = "DEVICEHOSTNAME"
|
||||
|
||||
# Iterate List of Network Interfaces Remotely
|
||||
Invoke-Command -ComputerName $DEVICE -ScriptBlock { ipconfig /all }
|
||||
|
||||
# List Current DNS Servers for the selected interface
|
||||
Invoke-Command -ComputerName $DEVICE -ScriptBlock { Get-DnsClientServerAddress -InterfaceAlias "Ethernet" } | Select-Object Address
|
||||
|
||||
# Replace Current DNS Servers for the selected interface
|
||||
Invoke-Command -ComputerName $DEVICE -ScriptBlock { Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses ("192.168.3.25","192.168.3.26") }
|
||||
```
|
||||
Reference in New Issue
Block a user