Discovery - DNS (port 53) unresolved on every IP address in range
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2015 01:26 AM
Has anyone come across this prevously?
I've confirmed with our System & Network Admins and port 53 is open and not restricted, but during the Shazzam stage port 53 is always unresolved. I've sucessfully discovered multiple Linux servers (and CI's are created), but I get no DNS names either on the CI record or in the Discovery Scan results (see screenshot below).
I'm trying to implement discovery in a new Data center, but can't figure it out. It works perfectly fine from another MID Server into our other Data centers, so it's not the Probe or the configuration within ServiceNow. It's got to be a technical issue with the network or credentials, but I don't know what it could be.
Any help or previous experience would be greatly appreciated.
Thanks
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2015 02:38 PM
Scott,
Have you tried logging into the MID Server and running an nslookup to see if manually resolving DNS names works as expected? Would any of these devices have multiple DNS aliases for a single IP address/device?
Thanks
Brian