Questions about domain name resolution

Regarding domain name resolution, I have registered several domain names at domain name provider A: a1, a2, and a3. Among them, a1 is a frequently used website primary domain name.

A1 often encounters unresolved issues and confirms that it is not a cloud host (the ip address can be accessed normally ). Every time it takes a while and it returns to normal.

A1 cannot be resolved at the same time, a2, a3 is normal, ask the provider A that it is A browser problem, clear the cache COOKIE is still useless.
Executing nslookup a1 in CMD appears:
Server: unknow
Address: 192.168.0.1 ***** unknow cannot find a1: server failed

However, you can access the local link-properties-TCP/IPV4-custom DNS server 8.8.8.8 on your computer.




Where is the problem? have you ever talked about the same situation.

Reply to discussion (solution)

Why is it an intranet address?

It is estimated that your Lan has a ring
Generally, x. x. x.1 serves as the gateway. it may be a problem if you use it as the host at the same time.

Why is it an intranet address?

It is estimated that your Lan has a ring
Generally, x. x. x.1 serves as the gateway. it may be a problem if you use it as the host at the same time.

I started to doubt the router problem, but this problem also occurs in non-corporate networks.

If you change the DNS resolution, it means it is not a client problem.

The nslookup Lan address is a bit strange. isn't it because I checked the Internet address on the client?

In addition, the latest DNS has some actions, not to mention the reason
I have nearly 20 DNS shunting lines (China Southern telecom optical fiber line). The udp redirection of google dns, opendns, and comodo dns is serious, and tcp is normal.
Several other DNS services, such as 114dns, Alibaba dns, and several major Hong Kong dns services, are still "normal", while isp dns services are overloaded for many years without reference.

Therefore, when you confirm that everything is normal on the server, you should test the dns from an external line to eliminate the dns problem. internally, you should monitor the dns request status. it is best to analyze the visitor's path by yourself.

If you change the DNS resolution, it means it is not a client problem.

The nslookup Lan address is a bit strange. isn't it because I checked the Internet address on the client?

In addition, the latest DNS has some actions, not to mention the reason
I have nearly 20 DNS shunting lines (China Southern telecom optical fiber line). The udp redirection of google dns, opendns, and comodo dns is serious, and tcp is normal.
Several other DNS services, such as 114dns, Alibaba dns, and several major Hong Kong dns services, are still "normal", while isp dns services are overloaded for many years without reference.

Therefore, when you confirm that everything is normal on the server, you should test the dns from an external line to eliminate the dns problem. internally, you should monitor the dns request status. it is best to analyze the visitor's path by yourself.

If I use Alibaba DNS to resolve the domain name and set the TTL to a greater value, will it be more stable or less stable?

The error message shows the intranet address.
So this has nothing to do with public DNS, because the domain name has been resolved to your local site.
But your 192.168.0.1 cannot respond to the service.

Therefore, the most common problem is that there is a ring in the local network. you should first use the routing tool to check and eliminate the problem.
Because it is not absolutely inaccessible, there should be no problem with the ing table, but it is also necessary to check it.
Of course, dos attacks and ARP attack sources may also occur in the bureau.

This is basically related to the DNS resolution service.

The error message shows the intranet address.
So this has nothing to do with public DNS, because the domain name has been resolved to your local site.
But your 192.168.0.1 cannot respond to the service.

Therefore, the most common problem is that there is a ring in the local network. you should first use the routing tool to check and eliminate the problem.
Because it is not absolutely inaccessible, there should be no problem with the ing table, but it is also necessary to check it.
Of course, dos attacks and ARP attack sources may also occur in the bureau.

What tools are used for detection? This may happen elsewhere.

If you change the DNS resolution, it means it is not a client problem.

The nslookup Lan address is a bit strange. isn't it because I checked the Internet address on the client?

In addition, the latest DNS has some actions, not to mention the reason
I have nearly 20 DNS shunting lines (China Southern telecom optical fiber line). The udp redirection of google dns, opendns, and comodo dns is serious, and tcp is normal.
Several other DNS services, such as 114dns, Alibaba dns, and several major Hong Kong dns services, are still "normal", while isp dns services are overloaded for many years without reference.

Therefore, when you confirm that everything is normal on the server, you should test the dns from an external line to eliminate the dns problem. internally, you should monitor the dns request status. it is best to analyze the visitor's path by yourself.

If I use Alibaba DNS to resolve the domain name and set the TTL to a greater value, will it be more stable or less stable?
I think we should also look up the intranet. What DNS is used is about the client platform, and what people use has nothing to do with you. let's look at what the boss said.

It is estimated that there is no record filing !!!!!!!

I have encountered such a problem for a long time. it is the same as your response. I suggest you contact the domain name service provider.

I have encountered such a problem for a long time. it is the same as your response. I suggest you contact the domain name service provider.

The domain name provider said it was our reason. How did you solve it?

My current method is to set TTL to one day, so that only a few minutes of resolution will not be available in a day.