Zones on secondary have gone missing...

Re: Zones on secondary have gone missing...

From:

Date:

Time:

The only zone that shows up on the slave is the previously disabled
zone I mentioned. I re-enabled it. When I open the options for that
zone on the primary, I have a pull-down menu that shows both NS1 and
NS2.

However, any of the other 17 zones, when the options are selected for
them on the primary, do not give me an NS2 pulldown menu. All of the
zones, the one working and the seventeen not, have an NS2 nameserver
entry in their zone information.

The operating system on the slave is 9.1, as it has always been.
Operating system on the primary is 9.2.2, as it has always been. No
one else has the password to either server except me.

How would one configure a master zone to NOT be duplicated on the slave?

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.

Is it possible that the datafile for the slave server is corrupted?
Could I just delete it and let it rebuild from the primary server?

Jeff J.

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.
>

Sales:
888/4-DPOINT

Support:
858/452-3696