NPM checking website behind AWS ELB

Question

I have a website that sits behind an amazon ELB, so if you do a NSLOOKUP on x123.site.com you get aws-x123.us-east-1.elb.amazonaws.com and IP's of the web servers behind the load ball (2 ip address).

But whenever I try and add x123.site.com as a External Node to monitor (ssl & webpage) once I get to the last page "Change Properties" the name and IP have changed to the Host name of one of the webservers ec2-server.computer1.amazonaws.com and the IP of just that host. no longer the URL x123.site.com.

but going to the host name of the server wont resolve a webserver it needs to go through the ELB/ correct url. Any idea how to just check if the x123.site.com is working?

Thanks!

eayyyoh · Answer

when I ping

"ping x123.site.com" I get 
"Pinging aws-x123.us-east-1.elb.amazonaws.com [x.x.x.x] witch is one of the correct servers"

and if I do the -a x.x.x.x i get 
"pinging ec2-server.computer1.amazonaws.com"

the Orion server can go to website x123.site.com but if I try and go to aws-x123.us-east-1.elb.amazonaws.com that will not return the website.

adatole · Answer

If you RDP to the Orion server, how do you ping that website? Meaning:

* can you ping "x123.com" and get the correct IP address?
* can you ping -a x.x.x.x (the IP of x123.com) and get the correct URL back?

If those 2 things don't work in at the DOS prompt* on the Orion server, they won't work inside Orion itself

One work-around is to update the hosts file (C:\windows\system32\drivers\etc\hosts) with the IP and name so that it resolves the way you want. THEN it should work in Orion too.

Remember that after you update the hosts file, you'll want to go to a DOS prompt* that's running with administrator privileges and run "nbtstat -R" to update the resolver tables.

* yes, it *IS* called "a DOS prompt". Because I'm old. And get off my lawn.