Developer Forum

I set up a Win2K server with DNS originally set as a Secondary to a Primay
DNS server running AIX. After a Zone Transfer of our Forward Lookup Zone, I
changed the DNS role to primary. All of the 4000+ records are in the
place.dns zone file in C:winnt\system32\dns directory and it is answering
queries beautifully. The only issue I have is that only the first 2000
records alphabetically show up in the GUI. When I reload or refresh the
Zone, the DNS console reports "There are too many items in the folder
x.x.edu. Please refine the query parameters or increase the maximum number
of items per folder." I can add records at will. I can delete records
from the GUI as long as they show up. It runs about halfway through the
"n"'s. If the record I add starts with A-N, then one less of the original
2000 shows up in a refresh/reload. Weird. I can't find anything on the web
about this. Any hits? Thanks, and Happy Holidays.

news.microsoft.com < XXXX@XXXXX.COM > posted their thoughts, then
I offered mine

The default should be 10000 objects. Goto View, Filter, Limit tab, and bump
it up.

Happy Holidays to you too!


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Unfortunately, that doesn't seem to help. I can set the View - Filter in
the DNS Console to 10000 and it still won't load more than 2000 entries.
I've created a test Forward Lookup Zone and it acts exactly the same. I can
populate it right up to 2000 entries and it will start barking on a
Reload/Refresh about too many items in the folder. This is very odd.

"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName& XXXX@XXXXX.COM > wrote in


then
bump

news.microsoft.com < XXXX@XXXXX.COM > posted their thoughts, then
I offered mine


That is strange because the 2000 records limit actually reminds me of the
ADUC limit in it's view. So I'm assuming that your zone is AD Integrated.
Here's a dumb suggestion (have no idea if it will work), goto ADUC and
change the default from 2000 to 10000. There may also be a setting one can
set using ADSI Edit to alter this. That I will have to dig for. If you have
ADSI Edit, look at your Domain NC properties. May be in there. Or even try
to make a new console?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Actually, I'm not AD yet. I'm migrating DNS from AIX in order to do the AD
upgrade next month. Never mind though. I went back and looked at the
place.dns file again. It's not 5K entries. It's 35K!! Sorry to send you
on a wild goose chase. It takes forever to reload, but it's working now.

One more question. The reason there are so many entries is that the Unix
admins always put a default hostname entry in when VLAN's were created (e.g.
vlan26_112). If I'm going to enable Dynamic DNs, do I need all the default
entries? Or should I parse out those and just leave the static entries for
specific machines. I know we only have about 10K devices on the network so
I've got 3 times the number of DNS entries as will really be used at this
time. Servers and some PC's get static entries. The rest will just
over-write the default names anyway.

"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName& XXXX@XXXXX.COM > wrote in


then
have

news.microsoft.com < XXXX@XXXXX.COM > posted their thoughts, then
I offered mine

Hmm, ok, I see now. No prob about the wild goose chase.

AS for Dnamic DNS, do you really need the clients registering? That has been
an off and on discussion. Not too many applications need a host record,
other than what they are directly using. Many schools/universities don't
register, since you'll get 10's of thousands of useless entries cluttering
your records, especially PDA, wireless, stuff like that, that just happen to
plug in for a short time and disappear. So that pretty much depends on your
needs.

As far as names, stay away from underscores in the names or you will find
errors generated due to them, such as Event ID 5504's. Stick with the RFC
names.
Here's some info on 5504's:
http://www.yqcomputer.com/

:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

I would love to not have my client PC's dynamically update DNS, but I must
be completely confused about DDNS. I was under the impression that I needed
to enable Allow Dynamic Updates on my Forward Lookup Zone in order to allow
for the creation of the appropriate SRV records by the first AD DC during
the upgrade from NT 4.0 next month. How can I allow that operation and deny
Dynamic Update to my 5000+ client PC's when they are in the same Forward
Lookup Zone?

"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName& XXXX@XXXXX.COM > wrote in


then
been
to
your

n news: XXXX@XXXXX.COM ,
news.microsoft.com < XXXX@XXXXX.COM > posted their thoughts, then
I offered mine

You can allow it jsut for the time for the DCs to register then turn it off.
If you make any changes in AD, need to allow it, then turn it off. While you
have it on, you can do this to force registration:

ipconfig /registerdns
net stop netlogon
net start netlogon

Wait for the data to register (when netlogon starts the service), then
disallow dynamic updates. Should work for you fine. If any clients get in
there during that time, delete them.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================