Ask the Community
Groups
FQDN is not resolved to device IP Address - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>QUESTION</strong></p> <p>When adding a new device by using the Fully Qualified Domain Name, the FQDN is not resolved to the device IP Address. How can the device be added in this scenario?</p> <p> </p> <p><img src="/attachments/token/3dnqlRWeKOX0zdOuDcqA4iUW6/?name=FQDN.png" alt="FQDN.png" width="855" height="428" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p><strong>RESOLUTION</strong></p> <p>Check the box 'Do Not Validate/Resolve Device Address'. This will allow the entry of a FQDN that will be resolvable at the remote location (by the DGEx) during monitoring.</p> <p>This does not impact monitoring of the device in any way.</p> <p> </p> <p><strong>APPLIES TO </strong></p> <p>All versions of Traverse.</p> <p><strong>REFERENCE </strong></p> <p>None.</p> </article> </main>