On the problem of domain name resolution

I have several domain names registered in Domain name provider a: A1,A2,A3. Where A1 is a frequently used site master domain name.

A1 frequently unresolved issues, confirming that the problem is not a cloud host (IP can be accessed normally). Each time it was a while back to normal.

A1 cannot parse while A2,a3 normal, ask provider A to say is the browser problem, empty cache cookie is still useless.
CMD execution nslookup A1 appears:
Server: Unknow
address:192.168.0.1 *****unknow can't find A1:server failed

However, you can access the local link-Properties-tcp/ipv4-custom DNS server settings 8.8.8.8 your computer.




The question is, where does it come from, or have you ever encountered the same situation?

Reply to discussion (solution)

Why is the intranet address?

I'm guessing there's a ring in your LAN.
General X.x.x.1 is as a gateway, you take him as a host, how much will be a bit of a problem

Why is the intranet address?

I'm guessing there's a ring in your LAN.
General X.x.x.1 is as a gateway, you take him as a host, how much will be a bit of a problem

I've also started to wonder about routers, but there are problems with non-corporate networks.

If you change a DNS resolution, this means that it is not the client's problem

Nslookup LAN address is a bit strange, not in the client check outside the network?

In addition the recent DNS a little action for reasons not to talk about
My side (Southern Telecom fiber line) hung nearly 20 DNS shunt, Google DNS, OpenDNS, Comodo DNS UDP switched serious, TCP is relatively normal
Several other DNS such as 114dns, Ali DNS, several major Hong Kong DNS are also "normal", the ISP's DNS load heavy for many years, do not reference

Therefore, in the case of confirming that the server is all right, you should test from the external line, troubleshoot DNS issues, internal monitoring of DNS request status, it is best to analyze the visitors ' antecedents

If you change a DNS resolution, this means that it is not the client's problem

Nslookup LAN address is a bit strange, not in the client check outside the network?

In addition the recent DNS a little action for reasons not to talk about
My side (Southern Telecom fiber line) hung nearly 20 DNS shunt, Google DNS, OpenDNS, Comodo DNS UDP switched serious, TCP is relatively normal
Several other DNS such as 114dns, Ali DNS, several major Hong Kong DNS are also "normal", the ISP's DNS load heavy for many years, do not reference

Therefore, in the case of confirming that the server is all right, you should test from the external line, troubleshoot DNS issues, internal monitoring of DNS request status, it is best to analyze the visitors ' antecedents

Then I use Ali DNS to resolve the domain name, and then the TTL set a little bit more stable or less this situation?

Your error message shows an intranet address.
So this has nothing to do with public DNS because the domain has been resolved to your gateway.
It's just your 192.168.0.1. Unable to respond to service

So the most common is the local network has a ring, should first use the Routing tool to check the exclusion
Because there is no absolute access, the mapping table should be fine, but it is also necessary to check it.
Of course, there are Dos attacks, ARP attack source in the network, it is also possible that this situation

This is basically related to the DNS parsing service.

Your error message shows an intranet address.
So this has nothing to do with public DNS because the domain has been resolved to your gateway.
It's just your 192.168.0.1. Unable to respond to service

So the most common is the local network has a ring, should first use the Routing tool to check the exclusion
Because there is no absolute access, the mapping table should be fine, but it is also necessary to check it.
Of course, there are Dos attacks, ARP attack source in the network, it is also possible that this situation

What tools are used for testing? This can happen elsewhere, too.

If you change a DNS resolution, this means that it is not the client's problem

Nslookup LAN address is a bit strange, not in the client check outside the network?

In addition the recent DNS a little action for reasons not to talk about
My side (Southern Telecom fiber line) hung nearly 20 DNS shunt, Google DNS, OpenDNS, Comodo DNS UDP switched serious, TCP is relatively normal
Several other DNS such as 114dns, Ali DNS, several major Hong Kong DNS are also "normal", the ISP's DNS load heavy for many years, do not reference

Therefore, in the case of confirming that the server is all right, you should test from the external line, troubleshoot DNS issues, internal monitoring of DNS request status, it is best to analyze the visitors ' antecedents

Then I use Ali DNS to resolve the domain name, and then the TTL set a little bit more stable or less this situation?
I think it's time to check the intranet, with what DNS that is the client platform, what they use nothing to do with you, see what the boss said

Estimated no filings!!!!!!!

I have encountered such problems, took a long time, and you respond to the same situation, I this is the domain name of DNS advice you or contact the domain name provider.

I have encountered such problems, took a long time, and you respond to the same situation, I this is the domain name of DNS advice you or contact the domain name provider.

The domain name quotient says is our reason, finally how did you solve?

My current approach is to set the TTL to one day, so that within a day there will only be a few minutes of unresolved situations.

