Shulou(Shulou.com)06/01 Report--

This article introduces the knowledge of "what to do if Linux cannot resolve a domain name". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Solution: 1. Check / etc/hosts # cat / etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4:: 1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.3 gus.xxxxxxxx.com2, view / etc/host.conf # cat / etc/host.conf order hosts Bind multi on3, View / etc/resolv.conf # cat / etc/resolv.conf search localdomain # nameserver 8.8.4.4 nameserver 8.8.8.8 initially used "nameserver 8.8.4.4" Resulting in an error in domain name resolution, and then changed to "nameserver 8.8.8.8" to resolve # ping gus.xxxxxxxx.com PING gus.xxxxxxxx.com (192.168.1.3) 56 (84) bytes of data. 64 bytes from ec192-1-3.ap-northeast-2.compute.amazonaws.com (192.168.1.3): this is the end of icmp_seq=1 ttl=39 time=458 ms's "what to do if Linux cannot resolve the domain name". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.