简体   繁体   中英

why EC2 /etc/resolv.conf is always got empty, and rebooting the instance can fill the values, but later on it will be empty again

Does anyone know the reason why the /etc/resolv.conf is got empty at sometimes and rebooting the instance, it can fill correct values into it, but after a while, it will be empty again, all the instances created by the same AMI have this issue.

the instances are under a VPC , and we have enabled DNS resolution and DNS hostnames , and even ClassicLink DNS Support .

and running dhcpclient doesn't work.

Can someone help? Thanks

It turns out to be the full disk issue, I have run out of disk space, so the dhcpclient cannot write content to the resolve.conf file, and if I reboot the instance then it got a little disk space, and dns resolution works fine, but after a while, it stops working because of no disk space.

Thanks.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM