Locked
Discussion interactions are currently paused.
Change to Default DNS Resolution on Services Functionality
Quick Version: It has come to our attention that there may be situations where some customers have services that are reporting as successful incorrectly. We are correcting that configuration during our Thursday maintenance window on May 5th (between 5:30 and 8:30pm PT, 00:30-03:30 UTC), so you may start getting new Services failures which reflect the correct status.
Longer Version: In some cases, if a customer misconfigured a Services URL such that it will fail public DNS resolution, the DNS failure would mistakenly be masked by resolution to a LogicMonitor wildcard DNS record and report a successful status. We are fixing this behavior in order to correctly report the DNS resolution error. In the course of this correction, the small number of users with unresolvable DNS names in URLs, may transition to a DNS failure state. If you find that you are starting to get alerts on a Service that previously worked fine, manage the settings on that service, and check that your domain is configured correctly.
Please contact support if you have any questions about this change or have trouble adjusting your Service as needed.
