<?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 named 9.3.2 zone transfer problem. in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5029996#M48266</link>
    <description>I am trying to troubleshoot a problem as to why when updates are made to our primary dns zones are not being updated with the changes. &lt;BR /&gt;&lt;BR /&gt;I have two identical boxes, both running FC6 with named9.3.2 .. &lt;BR /&gt;&lt;BR /&gt;We update the zone file in question on the primary, update the serial and restart the process. Do a dig on the secondary and the lookup fails.  My best guess is someone screwed up the zone file, tested against a zone that is working modified a record, and the transfer and lookup was successful. Does it sound like a zone file problem? &lt;BR /&gt;&lt;BR /&gt;To many danged hands in the cookie jar, our MSCE drives me nuts with his hunt and peck PICO crap and he likely jacked something up. this zone file is huge. I seem to recall there was a checkzone utility of some sort? &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 22 Feb 2007 10:46:27 GMT</pubDate>
    <dc:creator>rmueller58</dc:creator>
    <dc:date>2007-02-22T10:46:27Z</dc:date>
    <item>
      <title>named 9.3.2 zone transfer problem.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5029996#M48266</link>
      <description>I am trying to troubleshoot a problem as to why when updates are made to our primary dns zones are not being updated with the changes. &lt;BR /&gt;&lt;BR /&gt;I have two identical boxes, both running FC6 with named9.3.2 .. &lt;BR /&gt;&lt;BR /&gt;We update the zone file in question on the primary, update the serial and restart the process. Do a dig on the secondary and the lookup fails.  My best guess is someone screwed up the zone file, tested against a zone that is working modified a record, and the transfer and lookup was successful. Does it sound like a zone file problem? &lt;BR /&gt;&lt;BR /&gt;To many danged hands in the cookie jar, our MSCE drives me nuts with his hunt and peck PICO crap and he likely jacked something up. this zone file is huge. I seem to recall there was a checkzone utility of some sort? &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Feb 2007 10:46:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5029996#M48266</guid>
      <dc:creator>rmueller58</dc:creator>
      <dc:date>2007-02-22T10:46:27Z</dc:date>
    </item>
    <item>
      <title>Re: named 9.3.2 zone transfer problem.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5029997#M48267</link>
      <description>do you see the zone transfer message in the log file?&lt;BR /&gt;&lt;BR /&gt;is your secondary listed as NS for the domain?</description>
      <pubDate>Thu, 22 Feb 2007 13:20:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5029997#M48267</guid>
      <dc:creator>Wilfred Chau_1</dc:creator>
      <dc:date>2007-02-22T13:20:01Z</dc:date>
    </item>
    <item>
      <title>Re: named 9.3.2 zone transfer problem.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5029998#M48268</link>
      <description>This could be because:&lt;BR /&gt;&lt;BR /&gt;1- The slave server does not have the apropiate permissions to write to the zone directory/files. Ensure that the named user has all access to the zone directory/files.&lt;BR /&gt;&lt;BR /&gt;2- You are using DDNS. If you use DDNS, you must stop the DNS service, remove the .jnl zone file, update the zone and serial number, start the service.</description>
      <pubDate>Thu, 22 Feb 2007 13:29:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5029998#M48268</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-02-22T13:29:34Z</dc:date>
    </item>
    <item>
      <title>Re: named 9.3.2 zone transfer problem.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5029999#M48269</link>
      <description>Thanks all, find a typo courtesy of our microslop guy. Serial# mismatched.&lt;BR /&gt;&lt;BR /&gt;Corrected the SN and restarted seconday is updating. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Feb 2007 13:39:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5029999#M48269</guid>
      <dc:creator>rmueller58</dc:creator>
      <dc:date>2007-02-22T13:39:41Z</dc:date>
    </item>
    <item>
      <title>Re: named 9.3.2 zone transfer problem.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5030000#M48270</link>
      <description>thanks</description>
      <pubDate>Thu, 22 Feb 2007 13:40:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/named-9-3-2-zone-transfer-problem/m-p/5030000#M48270</guid>
      <dc:creator>rmueller58</dc:creator>
      <dc:date>2007-02-22T13:40:33Z</dc:date>
    </item>
  </channel>
</rss>

