<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ILO DNS Problem in Server Management - Remote Server Management</title>
    <link>https://community.hpe.com/t5/server-management-remote-server/ilo-dns-problem/m-p/6995255#M7973</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have problems reaching ILO with DNS Name in a not trusted domain. This domain is part of our company but for legal reasons separated.&lt;/P&gt;&lt;P&gt;The DNS of the not Trusted Domain is registered as secondary DNS Zone in our DNS Zone and my DNS Server registered as secondary DNS Zone in the not Trusted Domain.&lt;/P&gt;&lt;P&gt;DNS Name resolution works for Server and workstations but not for ILO.&lt;/P&gt;&lt;P&gt;Any idea how to solve this?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 30 Jan 2018 10:42:28 GMT</pubDate>
    <dc:creator>tomcat456</dc:creator>
    <dc:date>2018-01-30T10:42:28Z</dc:date>
    <item>
      <title>ILO DNS Problem</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ilo-dns-problem/m-p/6995255#M7973</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have problems reaching ILO with DNS Name in a not trusted domain. This domain is part of our company but for legal reasons separated.&lt;/P&gt;&lt;P&gt;The DNS of the not Trusted Domain is registered as secondary DNS Zone in our DNS Zone and my DNS Server registered as secondary DNS Zone in the not Trusted Domain.&lt;/P&gt;&lt;P&gt;DNS Name resolution works for Server and workstations but not for ILO.&lt;/P&gt;&lt;P&gt;Any idea how to solve this?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 10:42:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ilo-dns-problem/m-p/6995255#M7973</guid>
      <dc:creator>tomcat456</dc:creator>
      <dc:date>2018-01-30T10:42:28Z</dc:date>
    </item>
    <item>
      <title>Re: ILO DNS Problem</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ilo-dns-problem/m-p/6995259#M7974</link>
      <description>&lt;P&gt;Which ILO version is that?&lt;/P&gt;&lt;P&gt;Did you refer the ILO user guide to ensure the settings are right?&lt;/P&gt;&lt;P&gt;Also for testing, if you add it in the trusted DNS server, does it work alright?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 11:30:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ilo-dns-problem/m-p/6995259#M7974</guid>
      <dc:creator>RR33</dc:creator>
      <dc:date>2018-01-30T11:30:21Z</dc:date>
    </item>
    <item>
      <title>Re: ILO DNS Problem</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ilo-dns-problem/m-p/6995605#M7988</link>
      <description>&lt;P&gt;Hi, In addition to my good suggestions from my colleague. Maybe check if you use static or DHCP IP and if it makes a difference when you move to DHCP (with or without DHCP reservation at the backend for having always the same IP). I did run before into similair issues in our own lab where we had 2 different DNS zones liked you had and when doing the automatic DHCP and DNS integration by default from the DNSserver (dynamic dhcp mode in windows server DNS) then it would work as expected but with static DNS I could not get this to work properly.&lt;/P&gt;&lt;P&gt;Maybe it could help you?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Cheers, jeroen&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2018 11:00:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ilo-dns-problem/m-p/6995605#M7988</guid>
      <dc:creator>JeroenKleen</dc:creator>
      <dc:date>2018-01-31T11:00:22Z</dc:date>
    </item>
  </channel>
</rss>

