How to Change DNS on Starlink: Safe Router, Device and Rollback Steps

Independent guide: Starlink Tips is not part of Starlink. Menu names and available settings can vary by Starlink hardware, router and device software.

Changing DNS can help when a resolver is slow, filtered or unreliable, but it does not increase satellite capacity, fix obstructions or improve the radio link. The safest approach is to test first, change one layer at a time, and keep a simple rollback path.

What DNS changes on a Starlink network

DNS is the directory service that turns a name such as example.com into an address a device can contact. On a Starlink connection, DNS may be supplied by:

• the Starlink router;
• your own router, if the Starlink router is in bypass mode;
• an individual phone, tablet or computer;
• a VPN, security product or encrypted-DNS feature that overrides the local setting.

A standard Starlink router may not expose a custom-DNS field in the Starlink app. If that option is not available, do not hunt for a hidden setting or factory-reset the router. Set DNS on your own router or on the device you are testing.

Decide whether you need to change it

Leave DNS on automatic if websites and apps work normally. A custom resolver is worth testing when:

• several unrelated domains fail by name while other internet traffic works;
• lookups are consistently slow or time out;
• a filtering service is blocking a domain you need;
• you want to compare the result from your network with a known public resolver.

Changing DNS will not fix a service outage, a damaged cable, an obstruction, weak Wi-Fi or Starlink downtime. If only one website fails, test that website on mobile data first.

Record the current setup

Before changing anything, write down:

1. Whether you use only the Starlink router or a separate router.
2. Whether the separate router is in router mode, access-point mode or another layout.
3. Whether a VPN, ad blocker, parental-control service or security app is active.
4. The current DNS setting: automatic, provider-supplied or manually entered.
5. One or two domains that you can use for before-and-after testing.

Do not change the Starlink router, a separate router and the test device at the same time. That removes the evidence you need to tell which setting helped.

Test the baseline

Connect one device to the Starlink network and test a normal domain.

On Windows, open Command Prompt:

On macOS or Linux, open Terminal:

Replace example.com with the affected domain. Note whether the command returns an address quickly, times out, or reports a server failure. Repeat with a second unrelated domain. You are creating a baseline, not trying to prove that one lookup is perfect.

You can also compare a named resolver directly:

or:

Use the resolver address recommended by the provider you choose. Public examples such as 1.1.1.1 and 8.8.8.8 are only test values, not a guarantee that one provider is best for your location.

Choose the layer to change

If you use the Starlink router only

Set DNS on one test device first. This changes the behavior of that device without affecting the rest of the household.

A typical path is:

1. Open the device's network or Wi-Fi settings.
2. Open the details for the connected Starlink network.
3. Change DNS from automatic to manual.
4. Enter the primary and optional secondary addresses.
5. Save, disconnect from Wi-Fi, and reconnect.

The exact labels differ between Windows, macOS, iOS and Android. Use the operating system's current network instructions, and keep the original automatic setting recorded so you can restore it.

If you use your own router

Set DNS on the router only if you want the whole network to use it. Open the router's internet, WAN, DHCP or DNS settings, depending on the manufacturer. Enter the resolver addresses, save once, and allow the router to renew its connection.

If the Starlink router is in bypass mode, the separate router is normally the device handing out local network settings. If the separate router is only an access point, DNS may still be controlled by the upstream Starlink router. Check which device provides DHCP before changing anything.

Do not switch routing modes just to change DNS. That is a separate network decision and can create double NAT or disconnect local devices.

If a VPN or security service is active

A VPN, browser privacy feature or security product may deliberately use its own DNS. Test with that feature paused briefly, then turn it back on. If the result changes, adjust the service's DNS or split-tunnel policy instead of leaving protection disabled.

Some devices also offer encrypted DNS or private DNS. That setting can override the DNS address shown in ordinary Wi-Fi details, so check it when your manual change appears to have no effect.

Refresh and verify

After changing one layer:

1. Close and reopen the affected browser or app.
2. Disconnect and reconnect the device to Wi-Fi.
3. Flush the local DNS cache if your operating system supports that option.
4. Run the same lookup command again.
5. Test the affected site and a second unrelated site.
6. Repeat once on another device only if you changed the router.

A successful lookup does not prove that a website will load. Check the full path: name resolution, page loading, sign-in, uploads and any VPN or work application that matters to you.

Do not use an IP address from one lookup as a permanent replacement for a domain name. Web services change addresses and often rely on multiple records.

Roll back cleanly

Return the test device or router to automatic DNS when:

• the new resolver is slower;
• some sites work but others fail;
• captive portals or sign-in pages stop appearing;
• a VPN or security service behaves differently;
• you cannot explain the change in results.

Reconnect the device, repeat the baseline lookup and test the original problem again. If automatic DNS fixes the issue, leave it automatic and investigate the service or network layer that caused the earlier failure.

Common mistakes to avoid

• Changing every device first: Test one device so you can compare results.
• Assuming Starlink is the DNS setting: The Starlink router may simply pass settings to clients; a VPN or your own router may be in control.
• Confusing DNS with speed: DNS affects name lookup, not the capacity of the satellite link after a connection is established.
• Disabling security permanently: Use a brief test, then restore VPNs, filters and private-DNS protections.
• Mixing routing changes with DNS changes: Keep bypass mode, access-point mode and DNS as separate decisions.
• Testing one domain only: Use multiple unrelated domains and compare with mobile data when possible.

A short decision path

1. Confirm Starlink is online and other sites work.
2. Test the affected domain on another device and on mobile data.
3. Record the current DNS layer.
4. Test one known resolver without changing the whole network.
5. Change DNS on one device, or on the router if the whole network is affected.
6. Reconnect, repeat the lookup and test the real application.
7. Roll back if the result is slower, less reliable or unclear.

DNS is a useful, limited tool. Treat it as one controlled experiment inside the network, not as a replacement for diagnosing outages, Wi-Fi coverage, obstructions or hardware.

Related Starlink guides

• Some Websites Won't Load on Starlink? A DNS Troubleshooting Guide
• How to Set Up a Starlink DHCP Reservation for Stable Local IPs
• How to Use Starlink With a Wi-Fi Access Point Without Double NAT

Get One Month of Starlink Free

Claim Your Free Month

Order through my referral link and activate your service. Your second month of Starlink service will be free.