Singapore ISP DNS servers: Singtel, StarHub, M1 and ViewQwest

Applies to: Singapore broadband connections and DNS settings on routers, PCs and NAS devices. Managed business networks may require their own DNS servers.

Find the DNS servers your connection actually uses

1. Check the router first. Open its Internet or WAN status page and record the DNS addresses supplied by your ISP. A computer may show the router’s local address as its DNS server because the router forwards queries upstream.
2. Check one Windows computer. Open Command Prompt and run ipconfig /all. Find the active network adapter and its DNS Servers entry. Disconnect an unused VPN only if your administrator permits it; VPNs and office domains can intentionally supply different DNS.
3. Compare name resolution. Run nslookup aceperipherals.com and record the server used and the exact result. A timeout suggests a different problem from a valid “non-existent domain” reply. One failed lookup alone does not prove the ISP is down.
4. Change one device at a time. If an old manual DNS entry is no longer appropriate, return that device to automatic DNS and reconnect. Keep a record of the previous configuration. Do not replace office Active Directory DNS with a public resolver.
5. Recheck affected services. Test several websites and your NAS, VPN and business applications. Browser Secure DNS can use a different resolver from Windows, so compare both before changing the whole router.

Older ISP DNS addresses

These addresses were recorded in the earlier ACE guide. They are preserved for identifying an existing configuration, not as a verified current ISP recommendation. Confirm the addresses assigned to your service before entering them manually.

The earlier guide also listed SingNet mail hosts pop.singnet.com.sg and mail.singnet.com.sg. These are historical mail settings, not DNS resolver addresses; confirm current mail access and authentication with the provider.

Can I use a public DNS service?

Public resolvers are an alternative when your network policy allows them. Google Public DNS uses 8.8.8.8 and 8.8.4.4; Cloudflare uses 1.1.1.1 and 1.0.0.1. They do not repair a failed broadband line, bypass every service restriction or guarantee faster performance. Test one approved resolver pair on one device, then restore the previous setting if the problem remains.

Confirm the result

Lookups return sensible answers and the affected sites and internal services work. Record which change helped rather than assuming every connection problem was DNS.

If you need help

Include the ISP, router model, affected devices, whether wired access works, configured DNS addresses and the lookup error. Remove public IPs or internal domain details from any screenshot you intend to share publicly.

Updated 261108