Elasticsearch not accessible after moving from 1.4.4 to 2.0.0


I removed elasticsearch 1.4.4. using rpm. (It was installed using rpm package)

$rpm -e elasticsearch-1.4.4-1.noarch
Then installed 2.0.0 using rpm again and started it as below.

$rpm -ivh elasticsearch-2.0.0.rpm
$sudo chkconfig --add elasticsearch
$sudo service elasticsearch start

Logs show no error or exceptions

[2015-11-03 12:12:47,903][INFO ][node ] [Atalon] version[2.0.0], pid[4194], build[de54438/2015-10-22T08:09:48Z]
[2015-11-03 12:12:47,916][INFO ][node ] [Atalon] initializing ...
[2015-11-03 12:12:48,315][INFO ][plugins ] [Atalon] loaded [], sites []
[2015-11-03 12:12:48,781][INFO ][env ] [Atalon] using [1] data paths, mounts [[/ (/dev/mapper/vg01-LogVol00)]], net usable_space [37.2gb], net total_space [90.6gb], spins? [possibly], types [ext4]
[2015-11-03 12:12:59,073][INFO ][node ] [Atalon] initialized
[2015-11-03 12:12:59,073][INFO ][node ] [Atalon] starting ...
[2015-11-03 12:12:59,474][INFO ][transport ] [Atalon] publish_address {}, bound_addresses {}, {[::1]:9300}
[2015-11-03 12:12:59,567][INFO ][discovery ] [Atalon] elasticsearch/RNomvPO4TyyGpRdInlKZ7A
[2015-11-03 12:13:02,804][INFO ][cluster.service ] [Atalon] new_master {Atalon}{RNomvPO4TyyGpRdInlKZ7A}{}{}, reason: zen-disco-join(elected_as_master, [0] joins received)
[2015-11-03 12:13:02,931][INFO ][gateway ] [Atalon] recovered [0] indices into cluster_state
[2015-11-03 12:13:02,952][INFO ][http ] [Atalon] publish_address {}, bound_addresses {}, {[::1]:9200}
[2015-11-03 12:13:02,953][INFO ][node ] [Atalon] started

However, the curl command gives no response from elasticsearch.

curl -XGET http://localhost:9200

Network Error

Network Error (dns_unresolved_hostname)

Your requested host "localhost" could not be resolved by DNS.

For assistance, contact your network support team.

When used
curl -XGET
I get


localhost should always resolve to (and the other way around). Make sure you have          localhost

in your /etc/hosts. I have no explanation for the direction. What does it redirect to? What if you follow the redirection?