Search Again:

Re: Zones on secondary have gone missing...

From: Men & Mice Support
Date: Thursday, May 1, 2003
Time: 3:34:07 pm

"unloaded" means that it was removed from memory. In this case, it
probably means that the file QuickDNS Data:Secondary Domains was
altered, either by a human or by a file or disk corruption. Since all
your enabled slave zones were deleted but the disabled zone was
untouched, I would venture to guess that the entire Secondary Domains
file was replaced by a blank version - the disabled zone's settings
were stored in a separate file (Secondary Domains (disabled)) while
that zone was disabled.

Check your hard drive for corruption, just in case that was it. I
suggest Disk First Aid and/or Disk Warrior.
____________________________________________________________________
Chris Buxton Men & Mice
support@menandmice.com Making DNS Easy

At 4:35 PM -0500 5/1/03, Jeff Justice wrote:
>The log shows on April 13 at 10:19:47 all of the zones in question
>were unloaded at the same exact time/date stamp. So what does that
>indicate? What does "unloading" really mean? Does it mean deleted,
>and if so, how is that possible? I don't believe you can select a
>list of zones and delete them en masse.
>
>The one zone on the slave is now showing correctly. Thank you.
>
>Jeff J.
>
>
>On Thursday, May 1, 2003, at 04:24 PM, Men & Mice Support wrote:
>
>>At 4:11 PM -0500 5/1/03, Jeff Justice wrote:
>>>>>How would one configure a master zone to NOT be duplicated on the slave?
>>>>
>>>>When the zone was created, either you're not connected to ns2, or
>>>>else you unchecked ns2 in the new zone dialog. Or after the zone
>>>>was created, it was deleted from ns2.
>>>
>>>Okay. So, were back to square one. The zones either disappeared
>>>by themselves from the secondary, OR someone deleted them. Trust
>>>me, I would know if I'd deleted 17 zones, so I'm sure it wasn't
>>>me. Should I be able to find some record in the logs of where
>>>these zone went, who may or may not have been logged into the
>>>server etc? There has to be an explanation somewhere.
>>
>>You might be able to find when the zones were unloaded, shown in
>>the log. Otherwise, no.
>>
>>Starting with QuickDNS 4.0, QuickDNS Central maintains a zone
>>history for each zone. I'm not sure if it records zone deletion,
>>though.
>>
>>>>>Here's another note, when I double-click on the one zone that
>>>>>does show up on the slave, to bring up the zone details, it
>>>>>starts to come up, then gives me a dialog that says something
>>>>>like "Could not open the slave zone "elvinsrefrigeration.com."
>>>>>from the server ns2.starionhost.net.", probably because the zone
>>>>>data has not been transferred from the..." and it is cut off
>>>>>from there.
>>>>
>>>>That indicates that the zone was never transferred (via zone
>>>>transfer) from the master server. This could happen if, for
>>>>example, the zone is also disabled on the master server.
>>>
>>>The zone IS enabled on the master server. It is not updating the
>>>slave. It WAS disabled, but has been enabled now for more than an
>>>hour. The slave still shows it as disabled. Again, appears as if
>>>the slave is not updating.
>>
>>Enable it on the slave as well, and then see (in the slave server's
>>log) whether it transfers the zone from the master server. You
>>shouldn't have to wait for more than a few minutes to see how it
>>reacts to having the zone enabled.
>>____________________________________________________________________
>>Chris Buxton Men & Mice
>>support@menandmice.com Making DNS Easy
>>
>>>>>On Thursday, May 1, 2003, at 03:17 PM, Men & Mice Support wrote:
>>>>>
>>>>>>Yes, it is odd. What operating system are you using for the
>>>>>>slave server? When was the last time the disk was checked for
>>>>>>errors?
>>>>>>
>>>>>>Aside from computer error, the only explanation that comes to
>>>>>>mind is operator error. Has anyone besides yourself had the
>>>>>>password?
>>>>>>
>>>>>>The fact that zones still exist on the master server doesn't
>>>>>>mean that the slave server should also be configured for all of
>>>>>>them. While QuickDNS makes it easy to manage two servers
>>>>>>together, and create zones on both servers at the same time,
>>>>>>you can also use it otherwise. QuickDNS doesn't actively keep a
>>>>>>slave server up to date with a master server with regard to the
>>>>>>list of zones hosted on the two servers. (Zone contents
>>>>>>themselves should be kept up to date - when a zone changes on
>>>>>>the master server, the slave server should get the update in
>>>>>>short order.)
>>>>>>____________________________________________________________________
>>>>>>Chris Buxton Men & Mice
>>>>>>support@menandmice.com Making DNS Easy
>>>>>>
>>>>>>At 3:01 PM -0500 5/1/03, Jeff Justice wrote:
>>>>>>>I guess I don't understand why this happened at all. They
>>>>>>>used to be there. I haven't changed anything, and wouldn't
>>>>>>>the fact that they ARE set up in the primary mean they should
>>>>>>>be showing up in the secondary?
>>>>>>>
>>>>>>>Jeff J.
>>>>>>>
>>>>>>>
>>>>>>>On Thursday, May 1, 2003, at 02:04 PM, Men & Mice Support wrote:
>>>>>>>
>>>>>>>>It's not just that the slave server isn't updating; from what
>>>>>>>>you say, the slave server is not (or no longer) set up for
>>>>>>>>these zones at all.
>>>>>>>>
>>>>>>>>What version of QuickDNS are you using? Version 3.5 and later
>>>>>>>>have an AppleScript (included with the Mac version of
>>>>>>>>QuickDNS Manager) called "Add Slave Server" that will fix
>>>>>>>>this problem for you.
>>>>>>>>____________________________________________________________________
>>>>>>>>Chris Buxton Men & Mice
>>>>>>>>support@menandmice.com Making DNS Easy
>>>>>>>>
>>>>>>>>At 1:28 PM -0500 5/1/03, Jeff Justice wrote:
>>>>>>>>>I have two servers, primary, secondary. I don't have much
>>>>>>>>>need to look at them often as QuickDNS just WORKS (99.9% of
>>>>>>>>>the time :) ). However, today, I opened up my primary and
>>>>>>>>>secondary to add a new domain, and all of the zones, except
>>>>>>>>>one disabled zone I had, are gone from the secondary.
>>>>>>>>>
>>>>>>>>>Nothing has changed with the setup in months. I can ping
>>>>>>>>>the secondary, and the primary. I have rebooted the machine
>>>>>>>>>that the secondary is on. It appears that the secondary is
>>>>>>>>>not updating. Any ideas what has happened?
>>>>>>>>>
>>>>>>>>>Jeff J.




Messages In This Thread:



Return to Digital Point Solutions' Home Page