I am currently replacing a Windows 2000 server with a Windows 2003 server...

The Windows 2000 server has it's DNS configured to replicate 2 secondary
zones from a private network that it is connected to via a permanant wan.
On the windows 2000 server, this was no problem - you just set up the zone,
give it the DNS server ip address of the DNS server on the other network and
hey presto it works. The list of addresses appears and the dns server
resolves them correctly.

The windows 2000 server is still in the network (until I get the DNS working
on the new 2003 server).

The 2003 server (which is running AD - as was the 2000 server before I
depreciated it's role) has been set up in exactly the same way - ie setting
up the secondary zone, giving it the IP address of the DNS server for the
zone etc....

but...the zone shows as an error (red cross) - in the main window the
message is : "Zone Not Loaded by Server, The DNS Server encountered a
problem while attempting to load the zone. The transfer of zone data from
the master server failed. Correct the problem and press F5...... etc etc".

In an attempt to diagnose what is going on I run nslookup from the command
line, type in server dnsipfor zone and then try to resolve one of the
names within the zone. This works perfectly.

So, I'm now lost....

What can I do to diagnose whats going wrong?

Regards
Simon

In news:O1X6mlaJHHA.3424@TK2MSFTNGP02.phx.gbl,
Simon Verona <xx@xx.com> stated, which I commented on below:
> I am currently replacing a Windows 2000 server with a Windows 2003
> server...
> The Windows 2000 server has it's DNS configured to replicate 2
> secondary zones from a private network that it is connected to via a
> permanant wan. On the windows 2000 server, this was no problem - you
> just set up the zone, give it the DNS server ip address of the DNS
> server on the other network and hey presto it works. The list of
> addresses appears and the dns server resolves them correctly.
>
> The windows 2000 server is still in the network (until I get the DNS
> working on the new 2003 server).
>
> The 2003 server (which is running AD - as was the 2000 server before I
> depreciated it's role) has been set up in exactly the same way - ie
> setting up the secondary zone, giving it the IP address of the DNS
> server for the zone etc....
>
> but...the zone shows as an error (red cross) - in the main window the
> message is : "Zone Not Loaded by Server, The DNS Server
> encountered a problem while attempting to load the zone. The
> transfer of zone data from the master server failed. Correct the
> problem and press F5...... etc etc".
> In an attempt to diagnose what is going on I run nslookup from the
> command line, type in server dnsipfor zone and then try to
> resolve one of the names within the zone. This works perfectly.
>
> So, I'm now lost....
>
> What can I do to diagnose whats going wrong?
>
> Regards
> Simon

Without seeing your nslookup results and knowing which IP is which server,
etc, it's difficult to tell why nslookup works for you if the zone does not
exist, unless of course the machine you are running nslookup on is pointing
to a different DNS server.

Where is the Primary zone? Is it on a domain controller? If so, is it part
of the same domain or forest. If so, is the zone AD Integrated?

If no to the above, then I would simply delete the secondary zone, and
recreate it. This usually works. If yes to the above, then you can't make a
secondary zone on a DC with the same name of a zone that already exists in
the AD database. But a symptom of this is the zone you create simply
vanishes out of the console and is replaced by the zone that does exist in
the AD database.

--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

nslookup is definitely using the same DNS server (I'm typing server
[ipaddress] to force this).

I've deleted and recreated the zone on several occasions to no avail.

The DNS server is probably not a Windows machine (I have no idea to be
certain). It's certainly not part of te AD setup for this network (it's a
DNS server for a suppliers private network).

Is there anything more I can be doing?

In the meantime, can I import the name server list from the windows 2000
server to get it up and running (the addresses on the dns server rarely
change). ? If so then how ?

Thanks for you assistance.

Simon
"Ace Fekay [MVP]" <PleaseAskMe@SomeDomain.com> wrote in message
news:uLlDW8bJHHA.1008@TK2MSFTNGP06.phx.gbl...
> In news:O1X6mlaJHHA.3424@TK2MSFTNGP02.phx.gbl,
> Simon Verona <xx@xx.com> stated, which I commented on below:
>> I am currently replacing a Windows 2000 server with a Windows 2003
>> server...
>> The Windows 2000 server has it's DNS configured to replicate 2
>> secondary zones from a private network that it is connected to via a
>> permanant wan. On the windows 2000 server, this was no problem - you
>> just set up the zone, give it the DNS server ip address of the DNS
>> server on the other network and hey presto it works. The list of
>> addresses appears and the dns server resolves them correctly.
>>
>> The windows 2000 server is still in the network (until I get the DNS
>> working on the new 2003 server).
>>
>> The 2003 server (which is running AD - as was the 2000 server before I
>> depreciated it's role) has been set up in exactly the same way - ie
>> setting up the secondary zone, giving it the IP address of the DNS
>> server for the zone etc....
>>
>> but...the zone shows as an error (red cross) - in the main window the
>> message is : "Zone Not Loaded by Server, The DNS Server
>> encountered a problem while attempting to load the zone. The
>> transfer of zone data from the master server failed. Correct the
>> problem and press F5...... etc etc".
>> In an attempt to diagnose what is going on I run nslookup from the
>> command line, type in server dnsipfor zone and then try to
>> resolve one of the names within the zone. This works perfectly.
>>
>> So, I'm now lost....
>>
>> What can I do to diagnose whats going wrong?
>>
>> Regards
>> Simon
>
> Without seeing your nslookup results and knowing which IP is which server,
> etc, it's difficult to tell why nslookup works for you if the zone does
> not exist, unless of course the machine you are running nslookup on is
> pointing to a different DNS server.
>
> Where is the Primary zone? Is it on a domain controller? If so, is it part
> of the same domain or forest. If so, is the zone AD Integrated?
>
> If no to the above, then I would simply delete the secondary zone, and
> recreate it. This usually works. If yes to the above, then you can't make
> a secondary zone on a DC with the same name of a zone that already exists
> in the AD database. But a symptom of this is the zone you create simply
> vanishes out of the console and is replaced by the zone that does exist in
> the AD database.
>
> --
> Ace
> Innovative IT Concepts, Inc (IITCI)
> Willow Grove, PA
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Having difficulty reading or finding responses to your post?
> Instead of the website you're using, I suggest to use OEx (Outlook Express
> or any other newsreader), and configure a news account, pointing to
> news.microsoft.com. This is a direct link to the Microsoft Public
> Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows
> you to easily find, track threads, cross-post, sort by date, poster's
> name, watched threads or subject.
> It's easy:
>
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Infinite Diversities in Infinite Combinations
> Assimilation Imminent. Resistance is Futile
> "Very funny Scotty. Now, beam down my clothes."
>
> The only constant in life is change...
>

In news:%239HHVRcJHHA.1424@TK2MSFTNGP04.phx.gbl,
Simon Verona <xx@xx.com> stated, which I commented on below:
> nslookup is definitely using the same DNS server (I'm typing server
> [ipaddress] to force this).
>
> I've deleted and recreated the zone on several occasions to no avail.
>
> The DNS server is probably not a Windows machine (I have no idea to be
> certain). It's certainly not part of te AD setup for this network
> (it's a DNS server for a suppliers private network).
>
> Is there anything more I can be doing?
>
> In the meantime, can I import the name server list from the windows
> 2000 server to get it up and running (the addresses on the dns server
> rarely change). ? If so then how ?
>
> Thanks for you assistance.
>
> Simon

If they do not allow zone transfers, then No, you can't do it. Allowing zone
transfers are not enabled by default,otherwise everyone can copy a zone from
any machine on the internet. You will probably need to ask them. If they
already allowed you to be able to transfer the zone, you will also need to
allow inbound/outbound TCP 53 and UDP 53 to the 2003 machine from the source
(your supplier).

Ace

Ace

Thanks for the thoughts...

However, I probably didn't make it clear. I have a windows 2000 server
sitting on the same network that I want to retire and replace with the
Windows 2003 server.

The windows 2000 server runs these secondary zones perfectly... I've set
up the Windows 2003 server identically (as far as I can tell!).

Simon
"Ace Fekay [MVP]" <PleaseAskMe@SomeDomain.com> wrote in message
news:utjY$aiJHHA.420@TK2MSFTNGP06.phx.gbl...
> In news:%239HHVRcJHHA.1424@TK2MSFTNGP04.phx.gbl,
> Simon Verona <xx@xx.com> stated, which I commented on below:
>> nslookup is definitely using the same DNS server (I'm typing server
>> [ipaddress] to force this).
>>
>> I've deleted and recreated the zone on several occasions to no avail.
>>
>> The DNS server is probably not a Windows machine (I have no idea to be
>> certain). It's certainly not part of te AD setup for this network
>> (it's a DNS server for a suppliers private network).
>>
>> Is there anything more I can be doing?
>>
>> In the meantime, can I import the name server list from the windows
>> 2000 server to get it up and running (the addresses on the dns server
>> rarely change). ? If so then how ?
>>
>> Thanks for you assistance.
>>
>> Simon
>
> If they do not allow zone transfers, then No, you can't do it. Allowing
> zone transfers are not enabled by default,otherwise everyone can copy a
> zone from any machine on the internet. You will probably need to ask them.
> If they already allowed you to be able to transfer the zone, you will also
> need to allow inbound/outbound TCP 53 and UDP 53 to the 2003 machine from
> the source (your supplier).
>
> Ace
>

In news:eX5dhwmJHHA.3936@TK2MSFTNGP02.phx.gbl,
Simon Verona <xx@xx.com> stated, which I commented on below:
> Ace
>
> Thanks for the thoughts...
>
> However, I probably didn't make it clear. I have a windows 2000
> server sitting on the same network that I want to retire and replace
> with the Windows 2003 server.
>
> The windows 2000 server runs these secondary zones perfectly... I've set
> up the Windows 2003 server identically (as far as I can
> tell!).
> Simon

If the port remap (assuming that they are coming from an outside Master),
then the port remap has to go to the new server.

Ace