Hugh, Thank you. My problem seem to be ttl issue. The ttl for my records is one hour and this system was down longer than that due to power outage. Axfr dump from the Slave look as below. ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1 <<>> example.com axfr ;; global options: +cmd example.com. 3600 IN SOA srvyyzdc01.example.local. hostmaster.example.com. 2014111803 900 600 86400 3600 example.com. 3600 IN TXT "v=spf1 mx -all" example.com. 3600 IN MX 10 smtp1.example.com. example.com. 3600 IN NS srvyyzdc01.example.local. example.com. 3600 IN NS srvyyzdc02.example.local. example.com. 3600 IN A 192.168.230.241 aeo.example.com. 3600 IN A 192.168.230.131 Original Message From: D. Hugh Redelmeier Sent: Tuesday, November 25, 2014 5:35 PM To: GTALUG Talk Reply To: D. Hugh Redelmeier Subject: Re: [GTALUG] Cache DNS issues. | From: James Knott <james.knott@rogers.com> | The original TTL was 24 hours. How do you know that? Do you know the queries William Muriithi's machine is making? Do you know what DNS servers it is querying? In a response to a DNS query, each record has its own TTL. That TTL depends on what the authoritative server set it to be initially and how intermediate servers (if any) modified it (usually because it has been aging in a cache). You can see this with dig(1). --- GTALUG Talk Mailing List - talk@gtalug.org http://gtalug.org/mailman/listinfo/talk