DNS Zone shutdown

  • Thread starter Thread starter kwgm
  • Start date Start date
K

kwgm

The DNS Service event log contains errors 6527 within a
day or two of a server's boot.

This message tells me that a zone expires before zone
transfer can occur from a master, and the zone has been
shut down.

However, there never seems to be a problem with dns.

And I can manually get a zone transfer using the DNS
applet.

My network setup includes active server running in mixed
mode, with master dns zones in the NT domain.

Is this a problem with active server interoperating with
NT?

Can you shed light on why is this happening? Or refer me
to some information?

thanks in advance.

-- kwgm
(e-mail address removed)
 
In kwgm <[email protected]> posted a question
Then Kevin replied below:
: The DNS Service event log contains errors 6527 within a
: day or two of a server's boot.
:
: This message tells me that a zone expires before zone
: transfer can occur from a master, and the zone has been
: shut down.
:
: However, there never seems to be a problem with dns.
:
: And I can manually get a zone transfer using the DNS
: applet.
:
: My network setup includes active server running in mixed
: mode, with master dns zones in the NT domain.
:
: Is this a problem with active server interoperating with
: NT?

The NT4 secondary should do fine if they are SP4 or higher.

:
: Can you shed light on why is this happening? Or refer me
: to some information?
:


How do you have your zone transfers setup? To the nameservers listed on the
nameserver tab or to the physical IP of the NT4 secondary?
Is the Win2k set to notify the IP of the NT4 secondary.
Would the NT4 secondary be multihomed?
What is your SOA expire?
 
The secondary to primary "link" is done by physical IP
address.

The NT4 server is the primary and is set to notify the
Win2k Server (by IP address). I'm sorry, perhaps I wasn't
clear on this. The Win2k server is getting the error and
the zones are secondary to the NT4 server containing the
primaries. The NT4 is running SP6a. The Win2k is running
SP4 with most updates. All my servers are pretty well
updated.

The NT4 server (which is primary) is not multihomed now,
but has been in the past with same results.

The Win2k server is multihomed.

The SOA expirations are set at 24 hours. Is this too short?

Thanks for your quick reply.

--kwgm
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
: The secondary to primary "link" is done by physical IP
: address.
:
: The NT4 server is the primary and is set to notify the
: Win2k Server (by IP address). I'm sorry, perhaps I wasn't
: clear on this. The Win2k server is getting the error and
: the zones are secondary to the NT4 server containing the
: primaries. The NT4 is running SP6a. The Win2k is running
: SP4 with most updates. All my servers are pretty well
: updated.

Ok, so then we are not talking about an AD domain zone then.

:
: The NT4 server (which is primary) is not multihomed now,
: but has been in the past with same results.
:

: The Win2k server is multihomed.

That could be the problem if the Win2k is multihomed you need to allow zone
transfers to all IPs on the Win2k(secondary).
The DNS listener IP on a multihomed secondary DNS server is almost never the
same IP it connects to the primary from. If the secondary connects to the
primary from an IP different from the IP listed, zone transfers will fail.


:
: The SOA expirations are set at 24 hours. Is this too short?

Are the zones public domains?
If so, I think it is to short, public domains should be at least 7 days.
 
Hi,

Please check the settings of the expiration and refresh times on the primary
zone.

--
Regards,
Mohanchand Koduri [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
OR
If you wish to include a script sample in your post please add "Use of
included
script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
 
Back
Top