Re: error changing scope

From: Tommy Doan (tdoan_at_utdallas.edu)
Date: 07/06/04


Date: Tue, 6 Jul 2004 14:57:34 -0500

Thanks for the reply. Yes, I admit to cross posting to the W2k DNS board but
didn't know if the two enjoyed the same readership.

To answer Roger's questions, all DC's are at 2003 and the forest is 2003
native. The honest answer is that I am unsure whether any of the zones are
currently in application partitions. I'm embarrassed to say that I haven't
yet looked into creating application directory partitions; we brought the
current domains up under Windows 2000 did not make any major changes to DNS
after upgrading to 2003 last year. Really the only thing we did was change
the scope replication setting from the default "All DC's in the domain" to
"All name servers in the forest" when we added this 3rd name server; does
that alone create the application partition? One of the reasons I have not
yet done more is the fact that our two original name servers are slaves of a
Unix master that refuses (due to political reasons) dynamic updates. So the
top level of our forest is actually not owned by us. However we do own the
four underscore domains and the child domain that contains our two child AD
domains. Any help you can point me to would be greatly appreciated. I just
did a quick query on application partitions at microsoft.com and am going
over kb817470 now. Thanks again for the help.

"Roger Abell" <mvpNOSpam@asu.edu> wrote in message
news:uk8QDmMYEHA.2500@TK2MSFTNGP09.phx.gbl...
> OK, so clear up a few things for us.
> Three DNS servers, all on DCs, two in forestroot domain
> and new one in a child domain.
> Is the forest in W2k3 forest native mode ?
> It sounds as if your forward zones are already in DNS zone
> application partitions, but have you moved the reverse zone
> into one ??
> That message you cite, I am wondering if it is being given in
> error / is misleading. It soulds like the issue with W2k gold
> where there was a rather small number of names that could be
> bound on a NIC successfully - but that was fixed ages ago.
>
> --
> Roger Abell
> Microsoft MVP (Windows Server System: Security)
> MCSE (W2k3,W2k,Nt4) MCDBA
> "Tommy Doan" <tdoan@utdallas.edu> wrote in message
> news:%23d32bbHYEHA.2388@TK2MSFTNGP11.phx.gbl...
> > We have added a new name server in our 3 domain forest. The initial 2
> > servers are at the root domain; the new one will go into a child domain.
> > This requires a change in the replication scope from our original "All
> > domain controllers in the AD domain" to "All DNS servers in the forest."
> > However, when I try to change the scope for the reverse lookup zones on
> the
> > existing name servers, I consistently get an error. I had no problem
> setting
> > the scope on the new name server, and also had no problem changing the
> scope
> > on the forward lookup zones on the original name servers.
> >
> > The error states "The name limit for the local computer network adapter
> card
> > was exceeded." I was unable to find any helpful KB articles. Will I need
> to
> > remove all records from that zone first, then change the scope and wait
> for
> > replication to replace the records? Thanks.
> >
> >
>
>



Relevant Pages

  • Re: Pre-authentication failed for Windows 2008 systems
    ... This posting is provided "AS IS" with no warranties, ... If you are asking if the primary DNS zone contains A ... Active Directory Integrated Zones ... There are no WINS servers configured for this interface. ...
    (microsoft.public.windows.server.security)
  • Re: Forward lookup zone not automatically created for new domain in fo
    ... Company.biz is the forest root. ... forward lookup zones on the domain controllers hosting shell.company. ... You need your DNS servers in every domain/tree ... servers are Win2003 you can do forest wide AD Integration ...
    (microsoft.public.windows.server.active_directory)
  • Re: [fw-wiz] PIX, DNS fixups and Zone Transfers
    ... > We've recently implemented a PIX firewall setup, resulting in two DNS ... On the DNS servers, the ... > the current setup so that lookups by machines on the DMZ would work fine. ... Our DNS zones have one primary and 4 secondaries, ...
    (Firewall-Wizards)
  • Re: DNS resolving issue with new child domain
    ... What can you tell us about your DNS setup? ... Which zones are on which servers? ... Perhaps I should remove the dns server on the child domain and recreate it ...
    (microsoft.public.windows.server.dns)
  • RE: Sites and Services
    ... >> same as our existing Bind DNS name. ... Our Windows DNS servers then transfer the zones to ...
    (microsoft.public.windows.server.active_directory)