<?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: about named in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799083#M582452</link>
    <description>Just an FYI.  There is no need to restart the seconday server when you update the primary correctly.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 04 Sep 2002 17:36:27 GMT</pubDate>
    <dc:creator>Sean OB_1</dc:creator>
    <dc:date>2002-09-04T17:36:27Z</dc:date>
    <item>
      <title>about named</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799078#M582447</link>
      <description>hi expert,&lt;BR /&gt;   I want to change the configuration of name server,and  i modify the file in directory /etc/named.data, &lt;BR /&gt;if i want to apply the change, what should i do?&lt;BR /&gt;we have two dns server, one primary and one secondy, i am not sure just restart the named deamon will take the effect, if i also do any other action??</description>
      <pubDate>Wed, 04 Sep 2002 01:46:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799078#M582447</guid>
      <dc:creator>eric_88</dc:creator>
      <dc:date>2002-09-04T01:46:54Z</dc:date>
    </item>
    <item>
      <title>Re: about named</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799079#M582448</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The information in this posting should help you.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x650557bd90a9d611abdb0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x650557bd90a9d611abdb0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Michael</description>
      <pubDate>Wed, 04 Sep 2002 02:29:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799079#M582448</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2002-09-04T02:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: about named</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799080#M582449</link>
      <description>As per my under standing u need to restart named daemon at primary. kill -1 would be fine. not 100 % sure so do it with care&lt;BR /&gt;&lt;BR /&gt;kaps</description>
      <pubDate>Wed, 04 Sep 2002 02:32:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799080#M582449</guid>
      <dc:creator>KapilRaj</dc:creator>
      <dc:date>2002-09-04T02:32:39Z</dc:date>
    </item>
    <item>
      <title>Re: about named</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799081#M582450</link>
      <description>You need to increment the serial numbers in any database file you modified. Then run sig_named restart on the primary and then run sig_named restart on the secondary</description>
      <pubDate>Wed, 04 Sep 2002 17:07:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799081#M582450</guid>
      <dc:creator>Nashford Ramdeen</dc:creator>
      <dc:date>2002-09-04T17:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: about named</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799082#M582451</link>
      <description>Ok here goes.&lt;BR /&gt;&lt;BR /&gt;If you are adding a new zone (say a new domain you are now resolving) modify named.conf and add the zone entry.&lt;BR /&gt;&lt;BR /&gt;Then in the zone directory add the zone file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If you are just adding hosts to an existing zone edit the zone file.  Add the host, and make sure to update the serial number at the top of the zone file.  This is what is used to tell slaves that the zone has changed.&lt;BR /&gt;&lt;BR /&gt;Then do:&lt;BR /&gt;&lt;BR /&gt;ps -ef | grep named&lt;BR /&gt;find the process id and issue&lt;BR /&gt;&lt;BR /&gt;kill -1 pid-of-named&lt;BR /&gt;&lt;BR /&gt;This will recycle named and cause it to load the new zone file.  The slave servers will also realize that an updated zone is out there and should initiate a zone transfer of the updated zone.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 04 Sep 2002 17:35:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799082#M582451</guid>
      <dc:creator>Sean OB_1</dc:creator>
      <dc:date>2002-09-04T17:35:35Z</dc:date>
    </item>
    <item>
      <title>Re: about named</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799083#M582452</link>
      <description>Just an FYI.  There is no need to restart the seconday server when you update the primary correctly.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 04 Sep 2002 17:36:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-named/m-p/2799083#M582452</guid>
      <dc:creator>Sean OB_1</dc:creator>
      <dc:date>2002-09-04T17:36:27Z</dc:date>
    </item>
  </channel>
</rss>

