DNS Server Failure and Configuration Block | Generated by AI
The conversation revolved around persistent, severe network connectivity issues on the server (lzw-server).
Here is a summary of the events:
- The Problem: Initial requests to check
weibo.comviapingfailed with a “Temporary failure in name resolution,” and subsequent TCP connection attempts to various external services timed out (i/o timeout). - Diagnosis: We investigated DNS resolution using
nslookup, which confirmed the local DNS server (127.0.0.53) was actively refusing the queries. This indicated a local network configuration problem, not a website outage. - Root Cause: The configuration file (
/etc/resolv.conf) was managed bysystemd-resolved, pointing to the local stub resolver. - Proposed Solution: We determined the fix would likely involve changing the nameserver in
/etc/resolv.confto your gateway (192.168.1.1) to force external DNS lookups. - Roadblock: Attempts to modify this file using
exec(even with elevated privileges) failed with “Permission denied,” as the service aggressively manages the file. - Next Steps: The final advice was that if the file were changed, the DNS resolver service (
systemd-resolved) would need to be restarted for the changes to take effect.
In short: The server is having a fundamental problem resolving domain names because its internal DNS service is rejecting requests, and we were blocked from fixing the configuration due to file permission restrictions.