Internal server names no longer resolve, only IP addresses work
Your laptop reaches servers by IP but not by name. Almost always: your device is not talking to the right internal DNS server.
Try this first
- 1Open command prompt and run "ipconfig /all". See which DNS servers are listed under your active adapter.
- 2Is your internal DNS server (usually a local IP like 10.x.x.x or 192.168.x.x) at the top? If not, your laptop is asking internet DNS that does not know your internal names.
- 3On VPN: check that the VPN sets up "split DNS" correctly. Otherwise your laptop keeps using public DNS for everything.
- 4Test "nslookup servername" directly against the internal DNS server: "nslookup servername ip-of-DNS". Answer? Problem is in DHCP or VPN settings. No answer? Problem is on the internal DNS itself.
When to bring us in
Internal DNS often gets forgotten during maintenance. We tidy up stale records, ensure zone backups, and make sure colleagues never have to notice.
See also
- Wi-Fi drops randomly across the officeFirst rule out whether it is the access points or the internet connection itself. Different fix.
- One room or corner has no or bad Wi-FiNot always "add another AP"; often one is poorly positioned, or there is a metal wall in the way.
- Internet is suddenly slow for everyoneThree suspects: your provider, a colleague soaking the line, or a backup or update kicking in unexpectedly.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.