DNS problem

1.  Command Prompt. ...

2. Type ipconfig /flushdns and press ↵ Enter .
This command removes any saved DNS addresses. ...

10 Ways to Troubleshoot DNS

Resolution Issues
Introduction
We all need proper DNS resolution for our network applications. Let’s face
it, when DNS resolution is not working, using anything on your computer
that has to do with networking is painful because there is good chance it will
not work. DNS really is not a “nice feature” of a network, it is a requirement.
As a network admin, I have heard the alarming cry of end users moaning that
the network is down, when it would be the cause of the DNS servers. In these
cases I assure them that the network is up and running fine but it is the DNS
servers that are down! As you can imagine, that does not go over very well
with them because to an end user, it is all the same thing. DNS is “the
network” (not that they know what DNS is anyway).
So how do you troubleshoot this critical network infrastructure service when
you are on an end user PC (or your PC) and DNS is not resolving a DNS
name? Here are the 10 tips and tricks that I recommend you try to get DNS
working again…
1. Check for network connectivity
Many times, if you open your web browser, go to a URL, and that URL fails
to bring up a website, you might erroneously blame DNS. In reality, the issue
is much more likely to be caused by your network connectivity. This is
especially true if you are using wireless networking on a laptop. With
wireless security protocols, the key will be periodically renegotiated or the
signal strength will fade, causing a loss of network connectivity. Of course,
you can lose network connectivity on any type of network.
In other words, before blaming DNS for your problems, start troubleshooting
by checking “OSILayer 1 – Physical” first and then check your network
connectivity. Here you should find a wireless connection with a valid Internet
connection.

Figure 1: Good Wireless Network Connection

Notice how the Access is Local and Internet. If it just said “Local” then you
do not have a valid network address (you only have a private APIPA that
starts with 169.x.x.x).
This brings me to my next point. Make sure that you have a valid IP address
on your network. You can check this out by going to View Status on the
screen above and then to Details, you can check your IP address and verify
your DNS Server IP addresses. Again, if you have a 169.x.x.x IP address you
will never get to the Internet. Here is what it looks like:
Figure 2: Verifying your IP address and DNS Server IP addresses
2. Verify your DNS server IP
addresses are correct and in order
Once you know that you have network connectivity and a valid IP address,
let us move on to digging deeper into DNS by verifying that your DNS
Server IP addresses are correct and are in the right order.
If you look at Figure 2 above, you can see the IPv4 DNS Server IP
addresses. Notice that these are both on my local LAN / subnet so that I can
access them even if my default gateway is down. This is how it works on
most enterprise networks. However, your DNS servers do not always have to
be on your subnet. In fact, with most ISPs, the DNS Server IPs would not
even be on the same subnet as the default gateway.
In most home/SMB router configurations, they do not have their own DNS
servers and the SMB router is proxying DNS to the real DNS Servers. In that
case, your DNS Server IP address may be the same as your router.
Finally, make sure that your DNS Servers are in the right order. In my case,
with the graphic in Figure 2, my local DNS Server is 10.0.1.20. It is
configured to forward any names that it cannot resolve to 10.0.1.1, my local
router. That router is proxying DNS to my ISP’s DNS Servers. I can look up
those DNS Servers on my router, shown below in Figure 3.

Figure 3: My local DNS Servers, received from my ISP via DHCP
That brings me to two more points. First, make sure that your DNS Servers
are in the right order. If you have a local DNS Server, like I do, and you are
looking up a local DNS name, you want your PC client to lookup that local
DNS name in the local DNS Server FIRST, before the Internet DNS Server.
Thus, your local DNS server needs to be first in your DNS settings as these
DNS Server IPs are in the order that they will be used.
Secondly, you should be able to ping the IP address of your ISP’s DNS
Servers. So, just as my DNS servers are listed above on my router, I can
verify that I can ping them even from my local PC:

Figure 4: Pinging my ISP’s DNS Server

Notice how the response time from the ping to my ISP’s DNS Server is
horrible. This could cause slow DNS lookups or even failure if it takes too
long for the DNS server to respond.
3. Ping the IP address of the host you
are trying to get to (if it is known)
A quick way to prove that it is a DNS issue and not a network issue is to ping
the IP address of the host that you are trying to get to. If the connection to the
DNS name fails but the connection to the IP address succeeds, then you know
that your issue has to do with DNS.
I know that if your DNS Server is not functioning then it could be hard to
figure out what the IP address is that you want to connect to. Thus, to carry
out this test, you would have to have a network diagram or, like many
network admins do, just have the IP address of a common host memorized.
If this works, until the DNS server is available again, you could manually put
an entry in your hosts file to map the IP to the hostname.
4. Find out what DNS server is being
used with nslookup
You can use the nslookup command to find out a ton of information about
your DNS resolution. One of the simple things to do is to use it to see what
DNS server is providing you an answer and which DNS server is NOT. Here
is my nslookup of www.WindowsNetworking.com

Figure 5: nslookup output

Notice, in Figure 5, how my local DNS server failed to respond but my ISP’s
DNS server did provide me a “non-authoritative answer”, meaning that it
does not host the domain but can provide a response.
You can also use nslookup to compare the responses from different DNS
servers by manually telling it which DNS server to use.
5. Check your DNS suffix
If you are looking up a local host on a DNS server that your PC is a member
of, you might be connecting to a host and not using the FQDN (fully
qualified DNS name) and counting on the DNS suffix to help out. For
example, if I were to connect to “server1”, the DNS server could have
multiple entries for that DNS name. You should have your network adaptor
configured with the connection specific DNS suffix, as shown on the first
line on the graphic above, labeled Figure 1. Notice how in that graphic my
DNS suffix is wiredbraincoffee.com. Whenever I enter just a DNS name
like server1, the DNS suffix will be added on the end of it to make
it server1.wiredbraincoffee.com.
You should verify that your DNS suffix is correct.
6. Make sure that your DNS settings
are configured to pull the DNS IP from
the DHCP server
It is likely that you would want your network adaptor to obtain DNS Server
IP addresses from the DHCP Server.  If you look at the graphic below, this
adaptor has manually specified DNS Server IP addresses.
Figure 6: Verify DNS Server Settings
You may need to change to “Obtain DNS server address automatically” in
order to get a new DNS server IP. To do this, open the Properties tab of your
network adaptor and then click on Internet Protocol Version 4 (TCP/IPv4).
7. Release and renew your DHCP
Server IP address (and DNS
information)
Even if your adaptor is set to pull DNS information from DHCP, It is
possible that you have an IP address conflict or old DNS server information.
After choosing to obtain the IP and DNS info automatically, I like to release
my IP address and renew it.
While you can do this with a Windows Diagnosis in your network
configuration, I like to do it in the command prompt. If you have UAC
enabled, make sure you run the Windows cmd prompt as administrator then
do:
IPCONFIG /RELEASE
IPCONFIG /RENEW
Then, do an IPCONFIG /ALL to see what your new IP and DNS Server info
looks like.
8. Check the DNS Server and restart
services or reboot if necessary
Of course, if the DNS server is really hung, or down, or incorrectly
configured, you are not going to be able to fix that at the client side. You may
be able to bypass the down server somehow, but not fix it.
Thus, it is very likely that you, or the admin responsible for the DNS server,
need to check the DNS Server status and configuration to resolve your DNS
issue.
9. Reboot your small office / home
DNS router
As I mentioned above in #2 and showed in Figure 3, on home and small
office routers, the DNS server settings are typically handed out via DHCP
with the DNS server set to the IP of the router and the router will proxy the
DNS to the ISP’s DNS server.
Just as it is possible that your local PC has network info (including DNS
server IP Addresses), it is also possible that your router has bad info. To
ensure that your router has the latest DNS server information, you may want
to do a DHCP release and renew on the router’s WAN interface with the ISP.
Or, the easier option may be just to reboot the router to get the latest info.
10. Contact your ISP
We all know how painful it can be to contact an ISP and try to resolve a
network issue. Still, if your PC is ultimately getting DNS resolution from
your ISP’s DNS servers, you may need to contact the ISP, as a last resort.
 How to Fix DNS Server Not
Responding Problem
Five Parts:TroubleshootingFlushing the DNS CacheDisabling Extra ConnectionsEditing the DNS ServerResetting the

RouterCommunity Q&A

This wikiHow teaches you how to fix your PC's Internet connection issues that are
caused by Domain Name Server (DNS) errors. DNS is a server that translates websites'
addresses so that your browser can connect to them. If the addresses become out-of-
date or the server has issues, you'll encounter a DNS error and won't be able to connect
to a specific site or group of sites even with Internet access. You can potentially fix DNS
issues by troubleshooting your current connection, flushing the DNS cache, disabling
extra connections, changing your computer's default DNS server, and even resetting
your router.
Part 1

1
Try connecting with a different device. If you can connect a phone, tablet, or computer to the
network and access the webpage that you're having trouble with on your primary device, the
issue is definitively with the device and not the router.

 Not being able to connect with the second device doesn't necessarily mean that
the router is the problem.
 If you're having trouble with a specific website, try accessing it using mobile data.
If you still can't access the site, the issue is on the site's end.

2
Try a different browser. This is one of the quickest ways to test your DNS connections.
Download a different free browser such as Firefox or Chrome and attempt to connect to the
internet; if the problems persist, you can rule out browser problems as the reason for your DNS
server not responding.
 If the issues are resolved, uninstalling and then reinstalling your old browser will
likely fix the problem.

.3
Power cycle your modem and router. This will clear your router's cache and thus may resolve
DNS errors. To do so:
 Unplug your modem's power cable as well as your router's power cable.
 Allow both your modem and your router to sit for at least 30 seconds.
 Reconnect your modem and wait for it to come back online.
 Reconnect your router to your modem and wait for it to come back online.
.
 4
Connect your computer to your router via Ethernet. If you're already using Ethernet, skip
this step.

 If you can connect to a web page while using Ethernet, the problem may stem
from your router. You'll most likely need to reset it.
 If you can't connect to a web page while connected via Ethernet, your DNS
settings may be the problem.
Part 2
Flushing the DNS Cache: Mac

Windows

1. 1
Open Start 

 . Click the Windows logo in the bottom-left corner of the screen, or press  ⊞ Win .

2. 2
Type c o m m a n d p r o m p t  into Start. Doing so searches your computer for the Command
Prompt app.

3. 3
Click 

 Command Prompt. It's at the top of the Start window. This will open Command Prompt.
4. 4
Type in i p c o n f i g / f l u s h d n s  and press  ↵ Enter . This command removes any saved

DNS addresses. The next time you try to open a website, a new DNS address will be created.

5. 5
Restart your web browser. Doing so refreshes your browser's cache. If you can now connect
to the webpage you were having trouble with earlier, the problem is resolved.
 If you're still experiencing connection issues, proceed to the next method.

Mac

1. 1
Open Spotlight 

 . It's in the top-right corner of the screen.

 You can also press  ⌘ Command + Space  to open Spotlight.

.2
Type t e r m i n a l  into Spotlight. Spotlight will begin searching for Terminal on your Mac.

.3
Click 

 Terminal. It should be the first option at the top of the Spotlight results.
 .4
Type this command into Terminal: 
sudo killall -HUP mDNSResponder
and press  ⏎ Return . This will restart the macOS DNS process.

 You may have to enter your administrator password first.

.5
Restart your web browser. This refreshes your browser's cache as well. If you can now
connect to the webpage with which you were having issues, the problem is resolved.
Part 3
Disabling Extra Connections

1. 1
Open your computer's Network Settings.
 On Windows: Open Start 

 , click Settings 

 , click 

 Network & Internet, and click Change adapter options.

 On Mac: Open the Apple menu 

 , click System Preferences, and click Network.

 .2
Look for extra connections. You can remove any connection to which you aren't currently
connected; this includes Bluetooth and wireless connections.
 The most common cause for DNS issues is the existence of "Microsoft Virtual
WiFi Miniport Adapter".[1]

.3
Select an extra connection. Simply click a connection to select it.
 On Windows, each icon on the page represents a connection.
 On Mac, the connections are on the left side of the window.

.4
Remove the connection. To do so:
 Windows - Click Disable this network device at the top of the window.
 Mac - Click the minus sign (-) at the bottom of the network window.

.5
Try visiting a webpage. If you can access your webpage, then the issue is resolved. If not,
proceed to the next method.
Part 4
Editing the DNS Server: Mac

Windows

1. 1
Click your current connection's name. It will be on the Connections page. This will select it.
2. 2
Click  Change settings of this connection . This button is in the top row of options in the
window. Clicking it will open the connection's settings.

3. 3
Click the "Internet Protocol Version 4 (TCP/IPv4)" result. It's in the window that's in the
middle of the Wi-Fi Properties pop-up. Doing so will select it.
 If you don't see this window, click the Networking tab at the top of Wi-Fi
Properties.

.4
Click  Properties . This option is near the bottom of the window.

.5
Check the "Use the following DNS server addresses" circle. It's near the bottom of the
Properties window.

.6
Enter a preferred DNS address. This goes in the "Preferred DNS server" field near the bottom
of the window. Reliable DNS servers include the following:
 OpenDNS - Enter 2 0 8 . 6 7 . 2 2 2 . 2 2 2 .
 Google - Enter 8 . 8 . 8 . 8 .

.7
Enter an alternate DNS address. This goes in the "Alternate DNS server" field below the first
field. Depending on what you entered in the "Preferred" field, what you enter here will vary:
 OpenDNS - Enter 2 0 8 . 6 7 . 2 2 0 . 2 2 0 .
 Google - Enter 8 . 8 . 4 . 4 .

.8
Click  OK . Doing so saves your DNS settings.

.9
Click  Close . It's at the bottom of the window.

. 10
Restart your computer. Once your computer finishes booting up, you can test your network
connection; if it works now, your computer's default DNS server was the problem.
 If your computer can connect, consider calling your Internet Service Provider to
notify them about the DNS issues.
 If you still can't connect, proceed to the next method.

Mac

1. 1
Open the Apple menu 

 . It's in the top-left corner of the screen.

2. 2
Click  System Preferences . You'll find it near the top of the Apple drop-down menu.
3. 3
Click  Network . This globe-shaped icon is in the System Preferences window.

4. 4
Click your current Wi-Fi network. It's in the pane on the left side of the window.

5. 5
Click  Advanced . You'll find this near the middle of the window.

6. 6
Click the  DNS  tab. It's at the top of the window.

7. 7
Click  + . This option is below the DNS Servers window.

8. 8
Enter a DNS server address. OpenDNS and Google both have reliable, quick DNS servers:
 Google - 8 . 8 . 8 . 8  or 8 . 8 . 4 . 4 .
 OpenDNS - 2 0 8 . 6 7 . 2 2 2 . 2 2 2  or 2 0 8 . 6 7 . 2 2 0 . 2 2 0

.9
Click the  Hardware  tab. It's on the far-right side of the tabs at the top of the window.

. 10
 Click the "Configure" box, then click  Manually . This box is near the top of
the Hardware page.

. 11
Click the "MTU" box, then click  Custom . The "MTU" box is below the "Configure" box.

. 12
Type 1 4 5 3  into the text field. It's below the "MTU" box.

. 13
Click  OK . It's at the bottom of the page.

. 14
Click  Apply . This button is at the bottom of the page. Doing so saves your settings and applies
them to your current Wi-Fi network.

. 15
Restart your computer. Once your computer finishes booting up, you can test your network
connection; if it works now, your computer's default DNS server was the problem.
 If your computer can connect, consider calling your Internet Service Provider to
notify them about the DNS issues.
 If you still can't connect, proceed to the next method.
Part 5
Resetting the Router

1. 1
Find your router's "Reset" button. This button is usually on the back of the router.
 You'll usually need a needle, a paperclip, or a similarly thin item to press the
"Reset" button.
 Resetting your router will also disconnect every device you have connected to
the router.

.2
Press and hold the "Reset" button. Hold it for at least 30 seconds to ensure that the router
completely resets.

.3
Connect to your network. Use the factory password that's printed on the bottom of your router
to complete the connection.

.4
Try accessing the website you were having trouble with. If you still can't connect to the
Internet or access the site you're trying to use, it's time to contact your Internet Service Provider
to make them aware of the DNS issues you're facing.

 If resetting the router does indeed resolve the DNS issues, consider picking up a
newer router if yours is more than a couple of years old.