VPN Configure logoVPN Configure
GuidetroubleshootingBeginner

Best DNS for PS5 (2026): Primary & Secondary Settings

Try Cloudflare 1.1.1.1 / 1.0.0.1 or Google 8.8.8.8 / 8.8.4.4 on PS5. Follow the setup steps, test your connection, and see why DNS does not directly lower ping.

VPN Configure editorial shield

Networking Editorial

PlayStation 5PlayStation 5 DigitalPlayStation 4Router
PlayStation 5 console beside a TV showing the network settings screen
Changing DNS on a PS5 takes about two minutes and is reversible at any time.

Quick Answer

Start by testing Cloudflare: Primary DNS 1.1.1.1, Secondary DNS 1.0.0.1. Google Public DNS (8.8.8.8 and 8.8.4.4) is another option. There is no fastest DNS for every PS5 or Wi Fi connection: compare either pair with Automatic on your own network. A resolver change can help when DNS lookups are slow or failing; it does not directly lower in game ping, increase line bandwidth, or change NAT type. You do not need to buy a VPN or a DNS subscription to use these public resolvers.

What DNS Actually Changes on a PS5

DNS is the lookup step. Before your console connects to a service, it translates the service hostname into an IP address. Automatic DNS usually uses a resolver supplied by your router or ISP. If that resolver is slow or fails, testing a public resolver can help. The improvement depends on your network and cached responses; we have not measured a universal time saving.

PlayStation Network sign in, the store and game services can all depend on DNS. Once a connection is established, its ongoing latency is not determined by how fast the original lookup completed. DNS can sometimes affect which download endpoint a service selects, but that is not a guaranteed bandwidth or ping improvement.

Best DNS Servers for PS5 in 2026

ResolverPrimarySecondaryBest for
Cloudflare1.1.1.11.0.0.1General purpose resolver to compare with Automatic
Google Public DNS8.8.8.88.8.4.4Alternative general purpose resolver to test
Quad99.9.9.9149.112.112.112Blocks known malicious domains
OpenDNS208.67.222.222208.67.220.220Household filtering options via a free account
Cloudflare Family1.1.1.31.0.0.3Blocks adult content on shared family consoles
Public resolvers worth testing on a PlayStation 5

There is no single winner for every household. The resolver that is fastest for you depends on which datacentre your ISP peers with. Test two pairs, keep the one that measures better, and move on; the difference between the top two is usually small.

How to Change DNS on a PS5, Step by Step

  1. Open the network settings

    From the home screen go to Settings, then Network, then Settings, then Set Up Internet Connection.

  2. Pick your connection

    Highlight the Wi Fi network you use, or the LAN cable entry, press the Options button, and choose Advanced Settings. A wired connection is preferable if the console is near the router.

  3. Switch DNS to Manual

    Set DNS Settings to Manual. Leave IP Address Settings on Automatic unless you already run a static IP reservation.

  4. Enter the addresses

    Primary DNS 1.1.1.1 and Secondary DNS 1.0.0.1 for Cloudflare, or 8.8.8.8 and 8.8.4.4 for Google. Type them exactly; the console will not validate a typo until the connection test runs.

  5. Save and test

    Save the settings, then run Test Internet Connection. You want Internet Connection: Successful and PlayStation Network: Successful. Note the download and upload figures it reports.

  6. Restart the console

    A full restart clears cached lookups so the new resolver is actually used from the next session onward.

How to Tell Whether It Helped

Measure before you change anything, then measure again. Three checks are enough, and each takes under a minute.

  • Store responsiveness: time how long the PlayStation Store front page takes to fully draw, twice, before and after.
  • Matchmaking: note how long a standard online match takes to find a lobby in the game you play most.
  • Connection test: run the console's own Test Internet Connection three times and compare the average download figure, not one single run.

If nothing improves, revert DNS Settings to Automatic. The bottleneck is elsewhere, and keeping a manual resolver that gives you nothing only adds a thing to debug later.

DNS, NAT Type, and Ping: Three Different Problems

People often change DNS hoping to fix a Strict NAT or high in game ping. These are separate layers, and it helps to know which one you are actually fighting.

SymptomCauseActual fix
Slow store, slow patch startSlow DNS resolutionChange DNS as described above
NAT Type 3 / StrictRouter firewall and port mappingEnable UPnP, or port forward, and remove double NAT
High ping in matchesRoute and distance to the game serverUse a wired connection; pick a closer server region
Random disconnectsWi Fi interference or line instabilityMove to Ethernet; check for packet loss with your ISP
Download speed far below your planWi Fi band, congestion, or CDN throttlingUse 5 GHz or Ethernet; download during off peak hours
Which setting affects which symptom
NordVPN logo

NordVPN

$3.49/mo · 74% off · 30-day money-back guarantee

Get Deal

Common Mistakes

  • Mixing two different providers as primary and secondary. Keep the pair from one operator so failover behaves predictably.
  • Setting DNS on the console and a different DNS on the router, then wondering which one applies. The console setting wins for the console; keep them consistent.
  • Copying a random 'gaming DNS' IP from a video. Many of those addresses are dead, and a dead resolver means the console falls back and feels slower than before.
  • Expecting a resolver change to unblock a region locked store. It will not; store region is tied to the account, not to DNS.
  • Changing five things at once. Change DNS only, test, then move to the next variable.

Setting DNS on the Router Instead

If you want every device in the house to use the same resolver, set it once in the router's DHCP or WAN settings rather than on each console. The upside is consistency and one place to change later. The downside is that a mistake takes the whole network offline, so note the original values before you edit them. For consoles that also need a region change, a router level Smart DNS entry is the usual approach, and that is covered in the Smart DNS comparison guide.

A Note on Privacy

Your resolver sees every domain your console asks for. Moving from your ISP to Cloudflare or Google moves that visibility, it does not remove it. The PS5 does not support encrypted DNS natively, so lookups leave the console in plain text on the local network either way. If the goal is to keep browsing and gaming metadata away from your ISP entirely, a VPN on the router is the mechanism that does that, not a public resolver.

Frequently Asked Questions

What is the best DNS for PS5 downloads?

Test Cloudflare (primary 1.1.1.1, secondary 1.0.0.1) or Google (8.8.8.8 and 8.8.4.4) against Automatic on your network. Neither is a universal speed winner. DNS can affect address lookup and sometimes CDN selection, but it does not increase your line bandwidth or guarantee faster downloads.

Does changing DNS lower ping on PS5?

Not directly. Ping is decided by the route between your console and the game server. DNS only affects how quickly the address is looked up before the connection is made, so matchmaking can feel faster while in match ping stays the same.

Will DNS change my NAT type?

No. NAT type comes from how your router handles inbound connections. Enable UPnP or forward the ports your games need, and remove any second router in the chain.

Is it safe to use 1.1.1.1 on a console?

Yes. It is a public resolver run by Cloudflare and widely used. If you want malware filtering instead, Quad9 (9.9.9.9) is the equivalent option, and 1.1.1.3 adds adult content filtering for a family console.

How do I undo the change?

Go back to Settings, Network, Settings, Set Up Internet Connection, choose your connection, Advanced Settings, and set DNS Settings back to Automatic. The console returns to your ISP resolver immediately.

Should I set DNS on the PS5 or on the router?

On the console if only the PS5 needs it, on the router if you want the whole household on the same resolver. Do not set conflicting values in both places.