jthomp2127 Absent Member.
Absent Member.
1924 views

journal file corrupt

Hi all - we have 2 Netware 6.5 sp6 servers running DNS. They are the
primaries for most of our DNS but also secondaries to 4 AD DNS zones. These
zones are set up only to do transfers to one of the secondaries. When they
were set up the thinking was that since DNS is replicated in eDir then they
should not have to transfer to both. However, only the server that receives
the transfers gets the journal files created. The second server will start
throwing journal file corrupt errors. Shouldn't the transfers be set up to
go to both servers? The only information I found on the journal file is
pretty limited as to what it is actually used for in the zone transfer.
Anyone have any addition insight?


Labels (1)
0 Likes
9 Replies
Anonymous_User Absent Member.
Absent Member.

Re: journal file corrupt

This is not a common setup, so info may be hard to find about your
specific case. The first question that comes to mind is whether or not
everything else is working properly outside of the journal file errors?
If yes, it might be best to leave things alone.

bd
NSC Volunteer SysOp


0 Likes
jthomp2127 Absent Member.
Absent Member.

Re: journal file corrupt

Well - general DNS resolution still functions - at least for our primary
zone - I don't have the errors at the moment but when they happen it does
say critical error. Of course we point all the clients at both DNS servers
so they could still resolve correctly from the first server. When the errors
happen again I will try some resolution for devices in the transferred
zones. I'm just wondering if the second server is really updating properly
on these transferred zones....


"Morgan" <jthomp2127@yahoo.com> wrote in message
news:h_ZRj.8610$Dh4.3622@kovat.provo.novell.com...
> Hi all - we have 2 Netware 6.5 sp6 servers running DNS. They are the
> primaries for most of our DNS but also secondaries to 4 AD DNS zones.
> These zones are set up only to do transfers to one of the secondaries.
> When they were set up the thinking was that since DNS is replicated in
> eDir then they should not have to transfer to both. However, only the
> server that receives the transfers gets the journal files created. The
> second server will start throwing journal file corrupt errors. Shouldn't
> the transfers be set up to go to both servers? The only information I
> found on the journal file is pretty limited as to what it is actually used
> for in the zone transfer. Anyone have any addition insight?
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: journal file corrupt

In article <qp%Tj.10238$Dh4.9199@kovat.provo.novell.com>, Morgan wrote:
> I'm just wondering if the second server is really updating properly
> on these transferred zones....
>

Use NSLOOKUP to test that... you can point it to a single server,
independently of preconfigured DNS client settings.

bd
NSC Volunteer SysOp


0 Likes
jthomp2127 Absent Member.
Absent Member.

Re: journal file corrupt

Will do - just waiting for the error again. Had some strange problems this
weekend and the servers were rebooted a few times.

"Brad Doster" <bd@NSCSysOps.net> wrote in message
news:VA.00003f08.088ac9ee@nscsysops.net...
> In article <qp%Tj.10238$Dh4.9199@kovat.provo.novell.com>, Morgan wrote:
>> I'm just wondering if the second server is really updating properly
>> on these transferred zones....
>>

> Use NSLOOKUP to test that... you can point it to a single server,
> independently of preconfigured DNS client settings.
>
> bd
> NSC Volunteer SysOp
>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: journal file corrupt

OK, keep us posted...

bd
NSC Volunteer SysOp


0 Likes
jthomp2127 Absent Member.
Absent Member.

Re: journal file corrupt

OK - the error is back on the second server. Attaching a screen shot.



..net> wrote in message news:VA.00003f0a.2213e90b@nscsysops.net...
> OK, keep us posted...
>
> bd
> NSC Volunteer SysOp
>
>





0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: journal file corrupt

OK, I think I see what's happening. Each time an update occurs from
the MS server to the NW server, a new serial number for the zone is
included with the update. Serial numbers are the "trigger" to indicate
that changes have occurred and zone info needs to be updated. Then
after the update of just one of your NW servers, the NW second NW
server notices that the info in NDS has a new serial number, but it
doesn't know how it got there -- that's when the errors occur.

Fixing the problem could be tricky... if you have the MS server update
both NW Secondary servers (like would happen in a non-NDS environment),
it is still possible that the timing of events could have one NW server
checking the NDS info after the other has been updated, but before it's
received its updates from the MS server. If that happens, the only
real fix may be to maintain only one NW Secondary server, or maintain 2
NW Secondary servers, but in separate NDS trees so they don't compare
the NDS info with their local data.

bd
NSC Volunteer SysOp


0 Likes
jthomp2127 Absent Member.
Absent Member.

Re: journal file corrupt

Thanks for the info Brad. There is almost no documentation anywhere on
Netware DNS and DHCP as far as this level of detail. I appreciate it.....
"Brad Doster" <bd@NSCSysOps.net> wrote in message
news:VA.00003f0b.19be77ba@nscsysops.net...
> OK, I think I see what's happening. Each time an update occurs from
> the MS server to the NW server, a new serial number for the zone is
> included with the update. Serial numbers are the "trigger" to indicate
> that changes have occurred and zone info needs to be updated. Then
> after the update of just one of your NW servers, the NW second NW
> server notices that the info in NDS has a new serial number, but it
> doesn't know how it got there -- that's when the errors occur.
>
> Fixing the problem could be tricky... if you have the MS server update
> both NW Secondary servers (like would happen in a non-NDS environment),
> it is still possible that the timing of events could have one NW server
> checking the NDS info after the other has been updated, but before it's
> received its updates from the MS server. If that happens, the only
> real fix may be to maintain only one NW Secondary server, or maintain 2
> NW Secondary servers, but in separate NDS trees so they don't compare
> the NDS info with their local data.
>
> bd
> NSC Volunteer SysOp
>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: journal file corrupt

Glad to help!

bd
NSC Volunteer SysOp


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.