How to Edit the Hosts File as Administrator (2026)

Every operating system protects the hosts file behind administrator privileges. If you have ever seen "Access denied," "Permission denied," or a UAC prompt you dismissed — this guide explains why admin rights are required, how to properly elevate on each platform, and how to fix the most common permission errors.

See the main walkthrough: How to edit the host file on all platforms

Why admin rights are required

The hosts file is not a user document — it is a system configuration file that controls how your computer resolves every domain name. If any program could modify it silently:

• Malware could redirect your bank's domain to a phishing server
• Adware could inject ad-serving domains
• Attackers could intercept HTTPS by redirecting certificate validation domains

Operating systems therefore restrict write access:

Reading the file never requires admin rights. Writing always does.

Windows: Run as administrator

On Windows, membership in the Administrators group is necessary but not sufficient. User Account Control (UAC) requires explicit elevation for each editing session.

Correct method

1. Press Windows key, type Notepad 2. Right-click Notepad → Run as administrator 3. Click Yes on UAC 4. Open C:\Windows\System32\drivers\etc\hosts 5. Edit and Ctrl+S

What goes wrong

Opening Notepad normally, then navigating to the file You can open and edit the file, but saving fails with:

Cannot create the C:\Windows\System32\drivers\etc\hosts file.
Make sure that the path and file name are correct.

Or simply: Access is denied.

Fix: Close Notepad completely. Reopen with Run as administrator.

Opening the file from File Explorer double-click Same problem — File Explorer does not elevate Notepad automatically.

Fix: Always launch the editor as administrator first, then open the file from within the elevated editor.

PowerShell as administrator

# Open Terminal/PowerShell as administrator first, then:
notepad C:\Windows\System32\drivers\etc\hosts

Or edit inline:

Add-Content -Path C:\Windows\System32\drivers\etc\hosts -Value "127.0.0.1    mysite.test"

See Windows 11 guide for more methods.

Windows security features that block saves

Even with admin elevation, these can interfere:

Controlled Folder Access

• Settings → Privacy & security → Windows Security → Ransomware protection
• Add Notepad/VS Code/Terminal to allowed apps

Third-party antivirus

• Norton, McAfee, Kaspersky often "protect" the hosts file
• Look for "hosts file shield" or "DNS protection" in antivirus settings

Group Policy (corporate machines)

• IT may deploy policies that lock the hosts file
• Contact your administrator — do not attempt to bypass corporate security

macOS: sudo and root privileges

On Mac, /etc/hosts is owned by root:wheel with permissions -rw-r--r--. Only root can write.

Correct method

sudo nano /etc/hosts

Enter your account password (not root's — macOS admin accounts use sudo).

Save: Ctrl+O, Enter, Ctrl+X

What goes wrong

Editing without sudo

nano /etc/hosts
# Error: [ Error writing /etc/hosts: Permission denied ]

Using a GUI text editor without elevation TextEdit opened normally cannot save to /etc/hosts.

Fix for TextEdit (not recommended — use Terminal or Locahl):

sudo open -a TextEdit /etc/hosts

Forgetting your account is not admin Standard (non-admin) Mac accounts cannot use sudo. Check: System Settings → Users & Groups — your account should say "Admin."

See Edit hosts file on Mac.

Linux: sudo and root

Linux follows the same model as macOS — /etc/hosts owned by root.

sudo nano /etc/hosts
# or
sudo vim /etc/hosts

What goes wrong

User not in sudo group

user is not in the sudoers file. This incident will be reported.

Fix: Ask your system administrator to add you to the sudo group, or use su - to switch to root (if you have root password).

Editing as wrong user in multi-user systems Shared servers may restrict sudo via /etc/sudoers. Check with your admin.

Immutable flag set

lsattr /etc/hosts
# ----i---------e----- /etc/hosts
sudo chattr -i /etc/hosts  # remove immutable flag
# edit file
sudo chattr +i /etc/hosts  # restore if needed

See Linux guide and Ubuntu guide.

What NOT to do

Do not change file ownership

Bad (Windows): Taking ownership of hosts from SYSTEM to your user account weakens security and may break Windows Update behavior.

Bad (Mac/Linux):

sudo chown $USER /etc/hosts  # DON'T DO THIS

Always use elevation instead of ownership changes.

Do not chmod 666

Making the file world-writable allows any process to modify it — exactly what the OS tries to prevent.

sudo chmod 666 /etc/hosts  # NEVER

Correct permissions: -rw-r--r-- (644), owned by root.

Do not disable UAC permanently

Some tutorials suggest disabling UAC to "fix" access denied. This exposes your entire system to silent elevation by malware. Always use Run as administrator per session.

GUI tools and admin rights

Dedicated hosts file editors handle elevation for you:

• Locahl — prompts for admin password once, manages elevation automatically on Mac
• SwitchHosts — requires admin on each apply on Windows
• Gas Mask — macOS, handles sudo internally

Even GUI tools cannot bypass the underlying requirement — they just automate the elevation prompt.

Managed and corporate environments

If you cannot edit the hosts file despite following all steps:

1. Check Group Policy (Windows): gpedit.msc → look for DNS or hosts restrictions 2. Check MDM profiles (Mac): System Settings → Privacy & Security → Profiles 3. Check endpoint security logs for blocked writes 4. Ask IT — they may provide a approved process or deny hosts edits by policy

Developers on locked-down corporate laptops sometimes use:

• Remote development on a personal VM or cloud instance
• /etc/hosts equivalent in Docker --add-host
• DNS server they control (dnsmasq on a dev VM)

Verification checklist

After editing with proper admin rights:

Windows:

ipconfig /flushdns
ping mysite.test

macOS:

sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
ping mysite.test

Linux/Ubuntu:

sudo resolvectl flush-caches
getent hosts mysite.test

If resolution is correct, your admin elevation worked.

Quick reference by error message

Remote editing and SSH

On remote Linux servers accessed via SSH, you edit the server's hosts file — not your local machine's:

ssh user@staging-server
sudo nano /etc/hosts

This affects resolution on that server only. For local laptop resolution, edit your local hosts file. Confusing the two is a common mistake when debugging distributed systems — always confirm which machine's resolver you are configuring.

Audit your hosts file regularly

Schedule a monthly review:

# Mac/Linux — show non-comment lines
grep -v '^#' /etc/hosts | grep -v '^$'

# Windows PowerShell (admin)
Get-Content C:\Windows\System32\drivers\etc\hosts | Where-Object { $_ -notmatch '^s*#' -and $_.Trim() -ne '' }

Remove entries you do not recognize. Compare against your last known backup. Unknown redirects of financial, email, or antivirus domains warrant an immediate security scan.

Related guides

• Main guide — all platforms
• Windows 10
• Windows 11
• macOS
• Linux
• Ubuntu
• Permission denied on Mac
• Is editing safe?

---

*Last tested: Windows 11 24H2, macOS 15, Ubuntu 24.04 — June 2026.*