<?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: non-authoritative answer in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636986#M89803</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;This could be a security issue if the parent server of your DNS  is not secure(I think it should be out oy your own network). For example a hacker can hang that DNS and substitute it so he would be able to send you wherever he wants(for example a false page of Deutsche Bank). This can happen in any DNS from your DNS to the root servers but you can??t make anything about this. If you need to comunicate with some web site in a secure way use certificates.&lt;BR /&gt;&lt;BR /&gt;I hope this help.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 04 Jan 2002 15:05:03 GMT</pubDate>
    <dc:creator>oiram</dc:creator>
    <dc:date>2002-01-04T15:05:03Z</dc:date>
    <item>
      <title>non-authoritative answer</title>
      <link>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636984#M89801</link>
      <description>I have installed a linux box in the dmz and added the relative domain and dns entries in resolv.conf.  When I run nslookup from the linux box to a sub-dns inside the firewall I get non-authoritative answer which I understand means the sub-dns is not cached in the DMZ DNS database, correct?  My question is, is this a security issue?</description>
      <pubDate>Mon, 31 Dec 2001 14:44:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636984#M89801</guid>
      <dc:creator>lastgreatone</dc:creator>
      <dc:date>2001-12-31T14:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: non-authoritative answer</title>
      <link>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636985#M89802</link>
      <description>Hi,&lt;BR /&gt;Its very natural to behave in this way, and ther is no obvious security implications to it. You can have a look at the security and vulnerability trends at&lt;BR /&gt;&lt;A href="http://www.cert.org/present/cert-overview-trends/" target="_blank"&gt;http://www.cert.org/present/cert-overview-trends/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Manoj</description>
      <pubDate>Wed, 02 Jan 2002 06:55:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636985#M89802</guid>
      <dc:creator>Manoj Kumar Sarangi</dc:creator>
      <dc:date>2002-01-02T06:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: non-authoritative answer</title>
      <link>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636986#M89803</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;This could be a security issue if the parent server of your DNS  is not secure(I think it should be out oy your own network). For example a hacker can hang that DNS and substitute it so he would be able to send you wherever he wants(for example a false page of Deutsche Bank). This can happen in any DNS from your DNS to the root servers but you can??t make anything about this. If you need to comunicate with some web site in a secure way use certificates.&lt;BR /&gt;&lt;BR /&gt;I hope this help.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Jan 2002 15:05:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636986#M89803</guid>
      <dc:creator>oiram</dc:creator>
      <dc:date>2002-01-04T15:05:03Z</dc:date>
    </item>
    <item>
      <title>Re: non-authoritative answer</title>
      <link>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636987#M89804</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I completely agree with the previous answer.&lt;BR /&gt;&lt;BR /&gt;What I would suggest :&lt;BR /&gt;&lt;BR /&gt;Never put the reference DNS zones (aka primary or master or authoritative) in the DMZ. The Linux box in your DMZ should be a secondary (secondary) DNS server. It should synchronize with a primary server in your intranet through the firewall.&lt;BR /&gt;&lt;BR /&gt;To achieve this synchronization in a secure way, use cryptographic keys (available with BIND 8 and above). Read the named.conf manpage to learn more on this.&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;&lt;BR /&gt;Kodjo&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Jan 2002 00:45:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636987#M89804</guid>
      <dc:creator>Kodjo Agbenu</dc:creator>
      <dc:date>2002-01-08T00:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: non-authoritative answer</title>
      <link>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636988#M89805</link>
      <description>Hi,&lt;BR /&gt;  What nslookup is telling you is that the DNS server for the machine you are running nslookup on, is not one of the registered authoritative nameservers for your domain.  When nslookup starts, it lists the nameserver it is  using as a default.  By rights that wont be one of your registered nameservers.&lt;BR /&gt;If it is, you need to check your Internic records.   If it is you need to&lt;BR /&gt;check your zone files and particularly the NAMED.CONF file to make sure the&lt;BR /&gt;sure file are being loaded (primary) or transferred (secondary)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;Ramesh</description>
      <pubDate>Thu, 10 Jan 2002 04:29:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/non-authoritative-answer/m-p/2636988#M89805</guid>
      <dc:creator>ramesh_6</dc:creator>
      <dc:date>2002-01-10T04:29:23Z</dc:date>
    </item>
  </channel>
</rss>

