DNS - Secondary zone

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi
I have a Win2003 DNS AD integrated and a NT4-sp6a and I can't add a
secondary zone at the NT4 DNS
I have the following messages:

- Error creating zone: The new zone could not be created because there is
already a zone by this name. Verify that the zone name was entered correctly
or choose a new zone name.

- Dns.exe - application error: The memory could not be written

I'd like some help. Thanks in advance.
 
Glenn L said:
You really don't want to.
NT4 DNS does not support or understand SRV RR
Click to expand...

Although, I might agree with you that Win2000+ is better,
NT 4 with the later service packs does indeed support
SRV Resource Records and everyone should be running
the later service packs.

(I believe it started with SP4, but we are now on Sp6+ for
NT.)
 
In
Cami said:
Hi
I have a Win2003 DNS AD integrated and a NT4-sp6a and I can't add a
secondary zone at the NT4 DNS
I have the following messages:

- Error creating zone: The new zone could not be created because
there is already a zone by this name. Verify that the zone name was
entered correctly or choose a new zone name.

- Dns.exe - application error: The memory could not be written

I'd like some help. Thanks in advance.
Click to expand...

Prior to creating the zone, if you hit F5 to refresh it, does the zone show
up in the NT4 DNS manager?

Realistically, I really wouldn't use an NT4 DNS server in an AD
infrastructure, whether it supports SRVs or not.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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 Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Realistically, I really wouldn't use an NT4 DNS server in an AD
infrastructure, whether it supports SRVs or not.
Click to expand...

I might not "choose" NT4 but what is someone is still
running a location with no Win2000 and has an NT
server there?

What reasons (other than wanting to upgrade with which
I agree) woul you give for disliking NT4?
 
In
Herb Martin said:
I might not "choose" NT4 but what is someone is still
running a location with no Win2000 and has an NT
server there?

What reasons (other than wanting to upgrade with which
I agree) woul you give for disliking NT4?
Click to expand...

Lack of dynamic update capabilities. Lack of new beneficial features.
Possible vulnerabilities with exploits that no one has found, or even bother
testing for. It's old Herb, as you said, time to upgrade. Another scenario:
If a network has an AD infrastructure, and using an NT4 BDC at a remote
location with DNS installed, what happens with the newer clients and GPOs,
and other AD features? They need to traverse the WAN anyway, so why not just
upgrade it? Also, if the newer client tries logging on, and the BDC does not
respond fast enough, and it goes across the WAN to find another DC, and
finds an AD DC, then it changes it's authentication to Kerberos and won't go
back TO reset it, it needs to be dis-joined and rejoined in the proximity of
the NT4 BDC. (There's a tech article explaining that).If an app needs to run
on NT4, then I can understand. Preferably run it on an NT4 member, if
possible.

;-)

Ace
 
Back
Top