Forgive me, while the records are fully live on my internal servers, I configured the change for my external test server only (199.184.16.7, which is _probably_ available for external query) but not on the master.
We had issues years ago, and implemented a server parallel to the master to vet changes on, so if we lost a zone or crashed the server we could find that out without taking out the actual master. I did check the log files for my test server, there were no errors, the zone file seemed to reload without error and even noted the update in the soa serial number. > -----Original Message----- > From: Stephane Bortzmeyer [mailto:bortzme...@nic.fr] > Sent: Thursday, May 05, 2016 11:55 AM > To: Cuttler, Brian R. (HEALTH) <brian.cutt...@health.ny.gov> > Cc: bind-users@lists.isc.org > Subject: Re: Forward record for WWW > > ATTENTION: This email came from an external source. Do not open > attachments or click on links from unknown senders or unexpected emails. > > > On Thu, May 05, 2016 at 03:42:24PM +0000, Cuttler, Brian R. (HEALTH) > <brian.cutt...@health.ny.gov> wrote a message of 29 lines which said: > > > External record in the zone file is actually wadsworth.org. 300 IN A > > 199.184.16.22 > > None of the three name servers for wadsworth.org serve this A record. > > It seems the master was *not* reloaded. Did you check its BIND logs to > see? May be the new zone with the A record at the apex was rejected for > some reason. _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
