Zone file not updating

[Linux Addict]

Vinny Abello wrote:
> On Aug 20, 2008, at 1:19 PM, "Alan Clegg" <Alan_Clegg at isc.org> wrote:
>
>   
>> Linux Addict wrote:
>>     
>>> Nikolai Lusan wrote:
>>>       
>>>> On Tue, 2008-08-19 at 23:45 -0700, Nelson Serafica wrote:
>>>>         
>>>>> I'm updating the mx record in one of our hosted domain in our dns
>>>>> server. After I change the mx record of the zone file, I do rndc
>>>>> reload to apply the mx record and forward the copy to my secondary
>>>>> nameserver. However, when I do "dig mx <domain>", mx record doesn't
>>>>> change.
>>>>>           
>>>> So you edited the file and changed the value of some "foo IN MX <XX>
>>>> bar" line .. did you remember to update the serial in the SOA?
>>>>         
>>> It wont do immediately. Either you change the serial no or you have
>>> wait
>>> until the "refresh" time on your SOA expires so the master pushes the
>>> changes.
>>>       
>> Due to the way that updates work, if you don't increment your SOA, the
>> slave servers are NEVER going to get the update if you forget to bump
>> the serial number.
>>
>> Just Do It.
>>
>> AlanC
>>     
>
> One exception I can think of is if you erase the db file for the zone
> on the secondary name server and restart named. It would transfer a
> copy in this case on startup due to having no prior SOA to compare.
>
> That being said... Always update the serial number as has been stated.
> That's the way it was designed to work.
>
>
>   
rndc retransfer <Zone Name>