<?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: Reverse name resolution in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807559#M939792</link>
    <description>Reverse lookup is often forgotten by DNS administrators, especially if the DNS server is based on a PC or designed primarily for PC usage. However, it is crucial to require your DNS server to provide reverse lookup. It is a serious security risk (IP address spoofing) to not have this feature and commands like remsh, rlogin, rcp will fail.</description>
    <pubDate>Tue, 17 Sep 2002 16:50:30 GMT</pubDate>
    <dc:creator>ASO CENTRAL</dc:creator>
    <dc:date>2002-09-17T16:50:30Z</dc:date>
    <item>
      <title>Reverse name resolution</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807552#M939785</link>
      <description>Hi all&lt;BR /&gt;On my system when I do nslookup on hostnanme I do get the Ip 's attached to that host name .But when I do nslookup on Ip address I get name error.&lt;BR /&gt;Please help&lt;BR /&gt;Sandile</description>
      <pubDate>Tue, 17 Sep 2002 10:02:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807552#M939785</guid>
      <dc:creator>Sandile</dc:creator>
      <dc:date>2002-09-17T10:02:07Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse name resolution</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807553#M939786</link>
      <description>It would help if we knew what the DNS server is. Is it defined to do such?&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Tue, 17 Sep 2002 10:07:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807553#M939786</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-09-17T10:07:05Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse name resolution</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807554#M939787</link>
      <description>Hello Sandile,&lt;BR /&gt;&lt;BR /&gt;in the DNS server there must be two entries for every system. One entry is for name resolution (name --&amp;gt; ip), and one is for reverse name resolution (ip --&amp;gt; name). Seems that your dns tables are not up to date.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;Dirk</description>
      <pubDate>Tue, 17 Sep 2002 10:07:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807554#M939787</guid>
      <dc:creator>Dirk Wiedemann</dc:creator>
      <dc:date>2002-09-17T10:07:49Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse name resolution</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807555#M939788</link>
      <description>So do you do the DNS?&lt;BR /&gt;&lt;BR /&gt;If so, you are missing the&lt;BR /&gt;&lt;BR /&gt;db.reverse lookup files.&lt;BR /&gt;&lt;BR /&gt;these will look like db.1.168.192  for a domain of 192.168.1&lt;BR /&gt;&lt;BR /&gt;otherwise get in touch with your DNS admin</description>
      <pubDate>Tue, 17 Sep 2002 11:40:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807555#M939788</guid>
      <dc:creator>John Bolene</dc:creator>
      <dc:date>2002-09-17T11:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse name resolution</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807556#M939789</link>
      <description>laso try bouncing the named daemon on your DNS Server .</description>
      <pubDate>Tue, 17 Sep 2002 14:43:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807556#M939789</guid>
      <dc:creator>Ashwani Kashyap</dc:creator>
      <dc:date>2002-09-17T14:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse name resolution</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807557#M939790</link>
      <description>You might also check your /etc/hosts file.  &lt;BR /&gt;See if there is an error there.  &lt;BR /&gt;&lt;BR /&gt;Just a thought,&lt;BR /&gt;Rita&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Sep 2002 14:52:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807557#M939790</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2002-09-17T14:52:02Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse name resolution</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807558#M939791</link>
      <description>Hi Sandile,&lt;BR /&gt;&lt;BR /&gt;I agree with someone who posted an answer earlier, that you need to have a reverse hostname resolution (host to ipaddress and ipaddress to host).&lt;BR /&gt;&lt;BR /&gt;I think that should resolve your issues. This will happen only if you are getting the correct ipaddress when you do a nslookup for system name.&lt;BR /&gt;&lt;BR /&gt;If you don't pls let us know.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Anil</description>
      <pubDate>Tue, 17 Sep 2002 15:05:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807558#M939791</guid>
      <dc:creator>Anil C. Sedha</dc:creator>
      <dc:date>2002-09-17T15:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse name resolution</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807559#M939792</link>
      <description>Reverse lookup is often forgotten by DNS administrators, especially if the DNS server is based on a PC or designed primarily for PC usage. However, it is crucial to require your DNS server to provide reverse lookup. It is a serious security risk (IP address spoofing) to not have this feature and commands like remsh, rlogin, rcp will fail.</description>
      <pubDate>Tue, 17 Sep 2002 16:50:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807559#M939792</guid>
      <dc:creator>ASO CENTRAL</dc:creator>
      <dc:date>2002-09-17T16:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse name resolution</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807560#M939793</link>
      <description>Hi all&lt;BR /&gt;&lt;BR /&gt;Guys thanks very much for your support ,now it is working fine.Both dns files were there but now there was a problem with the named.boot file. I cleared the misprint there and now its working fine.</description>
      <pubDate>Wed, 18 Sep 2002 04:52:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reverse-name-resolution/m-p/2807560#M939793</guid>
      <dc:creator>Sandile</dc:creator>
      <dc:date>2002-09-18T04:52:57Z</dc:date>
    </item>
  </channel>
</rss>

