Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

DNS Location Monitor

Hi there,

I've been asked to put together a DNS location monitor using SAM. Not 100% i can actually do it this way, but basically the requirement is:

On the dashboard for our websites to have the primary location of the sites listed in a table.

There are 3 sites that could host each of the sites, so really all i need is something that will do an nslookup for the IP - and return a location (i.e. London) based on that IP. The only other option is to try and do it via SNMP on the Stingray Traffic Managers, but i havent had much luck with the MIB / SNMP on that!

Any pointers would be great

Cheers

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

Are these sites running on IIS? If so, are you using AppInsight for IIS? It sounds like the information you're looking for is located under each Site managed by AppInsight for IIS. You can check it out yourself at the link below.

http://oriondemo.solarwinds.com/Orion/APM/IisBlackBox/IisApplicationDetails.aspx?NetObject=ABIA:239

Selspiero

yeah, not exactly what i want - as the servers will show where you are regardless, we switch hosting between sites, so it would be useful to see where we are currently hosting from.

Thanks

silverbacksays

Maybe the Geolocation offered in 11.5 could help? See Rob's response in the following thread:

NPM 11.5 - Automatic Geolocation on WolrdWide Maps

You may be able to use this to show which node is hosting the IIS server which is hosting the website in question, effectively looking at it from a different perspective than just using DNS lookups.