<?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 Re: name resolution in isolated SLES9 system in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/name-resolution-in-isolated-sles9-system/m-p/4582634#M39730</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;If you can't talk to a DNS server, (see hosts entry in /etc/nsswitch.conf and /etc/resolv.conf) then use /etc/hosts networking&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;192.168.0.10  yourserver.yourdomain.com yourserver&lt;BR /&gt;192.168.0.20  netbackup.yourdomain.com netbackup&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Change to meet real names and IP addresses.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Thu, 11 Feb 2010 20:55:39 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2010-02-11T20:55:39Z</dc:date>
    <item>
      <title>name resolution in isolated SLES9 system</title>
      <link>https://community.hpe.com/t5/operating-system-linux/name-resolution-in-isolated-sles9-system/m-p/4582633#M39729</link>
      <description>I have a system running SLES9 that is in an isolated network.  I am trying to resolve the name of another system in this network but nslookup and host command want to resolve via DNS which is not possible.  I suspect that this is causing problems with the backup software, Datat Protector Express on this system since it can't resolve the backup servers name properly.  Is there a way configure this system to not look to DNS and resolve via hosts file?  Anyone familiar with DPX backup software?</description>
      <pubDate>Thu, 11 Feb 2010 20:09:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/name-resolution-in-isolated-sles9-system/m-p/4582633#M39729</guid>
      <dc:creator>Patrick Murphy</dc:creator>
      <dc:date>2010-02-11T20:09:08Z</dc:date>
    </item>
    <item>
      <title>Re: name resolution in isolated SLES9 system</title>
      <link>https://community.hpe.com/t5/operating-system-linux/name-resolution-in-isolated-sles9-system/m-p/4582634#M39730</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;If you can't talk to a DNS server, (see hosts entry in /etc/nsswitch.conf and /etc/resolv.conf) then use /etc/hosts networking&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;192.168.0.10  yourserver.yourdomain.com yourserver&lt;BR /&gt;192.168.0.20  netbackup.yourdomain.com netbackup&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Change to meet real names and IP addresses.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 11 Feb 2010 20:55:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/name-resolution-in-isolated-sles9-system/m-p/4582634#M39730</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2010-02-11T20:55:39Z</dc:date>
    </item>
    <item>
      <title>Re: name resolution in isolated SLES9 system</title>
      <link>https://community.hpe.com/t5/operating-system-linux/name-resolution-in-isolated-sles9-system/m-p/4582635#M39731</link>
      <description>You shouldn't have to configure the system, the hosts file just goes before the DNS when resolving names.</description>
      <pubDate>Fri, 12 Feb 2010 08:08:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/name-resolution-in-isolated-sles9-system/m-p/4582635#M39731</guid>
      <dc:creator>J. Maestre</dc:creator>
      <dc:date>2010-02-12T08:08:14Z</dc:date>
    </item>
  </channel>
</rss>

