<?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: Secondary DNS Updates in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/secondary-dns-updates/m-p/5108245#M49699</link>
    <description>When you changed the primary DNS zone data file, did you increment the serial number of the zone?&lt;BR /&gt;&lt;BR /&gt;The secondary server will check the serial number of the zone to find out whether the zone information has changed or not.&lt;BR /&gt;&lt;BR /&gt;The serial number is located in the SOA record of the zone. A common practice is to set the number as YYYYMMDDVV to document the date of the last change. The last two digits (VV) are a version number, so you can make 100 separate changes in one day, if necessary.&lt;BR /&gt;&lt;BR /&gt;However, the DNS servers interpret the serial number as just one big number, so the use of YYYYMMDDVV format is not mandatory. Just incrementing the serial number by 1 is enough to signal the secondary servers that some changes have been made.&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Sun, 11 May 2008 11:58:42 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2008-05-11T11:58:42Z</dc:date>
    <item>
      <title>Secondary DNS Updates</title>
      <link>https://community.hpe.com/t5/operating-system-linux/secondary-dns-updates/m-p/5108244#M49698</link>
      <description>Hello,&lt;BR /&gt;I have done a change in primary DNS server, and the change was successfull. When I chaeck the secondary dns server, even I have done the same updates, but still the old IP address is resoleved instead of the new one!!!&lt;BR /&gt;Thanks.</description>
      <pubDate>Sun, 11 May 2008 08:39:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/secondary-dns-updates/m-p/5108244#M49698</guid>
      <dc:creator>Fuad_1</dc:creator>
      <dc:date>2008-05-11T08:39:51Z</dc:date>
    </item>
    <item>
      <title>Re: Secondary DNS Updates</title>
      <link>https://community.hpe.com/t5/operating-system-linux/secondary-dns-updates/m-p/5108245#M49699</link>
      <description>When you changed the primary DNS zone data file, did you increment the serial number of the zone?&lt;BR /&gt;&lt;BR /&gt;The secondary server will check the serial number of the zone to find out whether the zone information has changed or not.&lt;BR /&gt;&lt;BR /&gt;The serial number is located in the SOA record of the zone. A common practice is to set the number as YYYYMMDDVV to document the date of the last change. The last two digits (VV) are a version number, so you can make 100 separate changes in one day, if necessary.&lt;BR /&gt;&lt;BR /&gt;However, the DNS servers interpret the serial number as just one big number, so the use of YYYYMMDDVV format is not mandatory. Just incrementing the serial number by 1 is enough to signal the secondary servers that some changes have been made.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Sun, 11 May 2008 11:58:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/secondary-dns-updates/m-p/5108245#M49699</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2008-05-11T11:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: Secondary DNS Updates</title>
      <link>https://community.hpe.com/t5/operating-system-linux/secondary-dns-updates/m-p/5108246#M49700</link>
      <description>Thanks it works.</description>
      <pubDate>Mon, 12 May 2008 04:50:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/secondary-dns-updates/m-p/5108246#M49700</guid>
      <dc:creator>Fuad_1</dc:creator>
      <dc:date>2008-05-12T04:50:26Z</dc:date>
    </item>
  </channel>
</rss>

