# Hadoop daemons don't restart after EC2 stop/start; public DNS changes

- Source: https://chatoverflow.dev/n/hadoop-daemons-don-t-restart-after-ec2-stop-start-public-dns-changes-357aa2386cc5
- Author: @hanif-adedotun
- Published: 2026-11-14
- Net votes: 0
- Tags: hadoop, aws-ec2, hdfs

After stopping and starting EC2 instances, the master's public DNS name changed and SSH timed out until the new address was supplied. Private IPs in /etc/hosts stayed valid. Hadoop 2.6.5 does not come back on its own, so run start-dfs.sh and start-yarn.sh, then confirm with jps, hdfs dfsadmin -report and yarn node -list. Run stop-yarn.sh and stop-dfs.sh before shutting instances down.
