The website cannot be opened due to an expiration problem during TTL transmission.

The website cannot be opened due to an expiration problem during TTL transmission.
The website cannot be opened due to the expiration of  TTL transmission.

Introduction:One of the depressing reasons is that the CSDN blog suddenly fails to be opened, and it won't work if I look at it. I think it's unreasonable,

It can be opened on a mobile phone or on another machine. Other websites are okay. It is too slow to open once in a while. What is the problem?

After installing the system a few days ago, I encountered a similar problem, that is, the local website and

Obfuscation occurs on the online website. I changed the host file. When I ping the domain name, I find that it is an online IP address.

This article also describes how to refresh the DNS cache.

Solution:

The query may be caused by a loop or an ARP virus attack on the LAN. Judging LAN security,

The first problem was found: loop problem ------ so the test experiment was conducted using the tracert command:

We can see that there is indeed a loop problem, and the data is starting to be okay, followed by a cycle of 98> 97

1. It may be a problem with the network itself, resulting in Loop Problems
Ii. Local dns problem: the problem can be solved by clearing the local DNS Cache using the following command.
There are two specific methods:
1. Close all browsers, right-click "Network neighbors", select "properties", right-click "Local Connection", and select "Repair.
2. In the DOS window (for XP, click "start", "Run" in the lower-left corner of the screen, and enter "cmd" and press Enter), enter ipconfig/flushdns to clear the DNS cache.

Certificate ------------------------------------------------------------------------------------------------------------------------------------------------------------

The solution is as follows:

1. Check whether the code is correct and whether the generation is successful

2. Is the IIS website configured correctly?

3. Whether the page path is correct

4. Check the HOST configuration file

5. ping the website domain name in the cmd command

6. Check IIS, adjust the port number, and ping the website domain name in the cmd command.

7. Finally, combine the above red font solution operations to basically refresh the DNS cache.

During IIS operations, restart