Kollektion / Studio / Motion
← Zurück zu Skripten

PowerShell-Skript zum Leeren des DNS-Caches

Wähle die DNS- und Netzwerkaktionen aus, die du brauchst, und kopiere anschließend den generierten PowerShell-Befehl.

Befehlsgenerator

Befehl erzeugen

Slugpowershell-script-flush-dns-cache
TypePowerShell-Skript
Befehlsvorschau Bereit

          

What this page helps you do

Build a command you can read before you run it

This page turns common network repair steps into one copy-ready command preview. You can decide whether you only want a fast DNS flush or a deeper refresh that also renews IP configuration and restarts an adapter.

When people use this script

Common situations where this change makes sense

Use it after DNS changes, when a domain still opens the wrong server, or when Windows keeps resolving an old address after a migration or router issue.

After you run it

Confirm the result in Windows instead of guessing

After you run the command, verify the related Windows setting or workflow instead of assuming every change applied exactly as expected. A quick manual check helps you catch edition differences, permissions issues, or app-specific behavior.

Before you make changes

Review the notes and choose only the options you actually need

Releasing and renewing IP configuration or restarting adapters can briefly disconnect the network. Save important work before running the more aggressive options.

Related pages

Open the next page that fits the same task

These links help you move from a command page to the matching Windows guide or browser tool without digging through the site again.

So verwendest du es

  1. Pick the DNS refresh level you want.
  2. Optionally select an adapter restart action.
  3. Copy the command block.
  4. Run it in PowerShell, then retry the website, server, or app that had the lookup issue.

FAQ

Fragen zu PowerShell-Skript zum Leeren des DNS-Caches

When is a DNS cache flush enough?

A simple cache flush is usually enough when a website or service has recently moved and Windows still points to an older address.

Why would I restart an adapter too?

Restarting the active adapter can help when the issue is not only stale DNS, but also a local network stack problem.