Re: DNS registration for PDC only correct on some DNS servers?



If you want to query external name servers for public names, you normally name their IP addresses as forwarders in the DNS server's
properties dialog.

I'm not quite sure what you're saying about putting NS entries under forward lookup zones. In Server 2003 you can name "conditional
forwarders" for specific domains that are different than the global forwarders. You are certainly free to add public zones to your
own DNS - I don't think it will do what you might expect, but as long as these zone names don't conflict with your internal AD
domain it shouldn't cause any problem there.

Are you sure you're not naming other, outside-the-domain DNS servers in the server's own DNS IP configuration? That would be the
most obvious reason for the error you're seeing, and can open the door to significant network problems.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.


"Kim Noer" <kn@xxxxxxxxx> wrote in message news:O8TjpwyeFHA.1448@xxxxxxxxxxxxxxxxxxxxxxx
> Hi there...
>
> Running netdiag I get this warning :
>
>
> DNS test . . . . . . . . . . . . . : Passed
> [WARNING]: The DNS registration for 'server.domain' is correct only on some DNS servers.
> Please wait 15 min for replication and run the test again.
> PASS - All the DNS entries for DC are registered on DNS server '10.0.0.200'.
>
> It confuses me slightly since there is only one DNS server in the domain, and it's running on the PDC (server.domain). Could this
> warning be related to external NS servers I've configured? With external I mean NS servers that look up on internet.
>
> I've configured those to NS servers under "forward lookup zones"->domain as NS.
>
> Presumeably that's not a correct setup? If so, then how do I correct setup external NS servers, whos sole purpose is to lookup
> domains on the internet (default route)?
>
> PS. server.domain is not the real name.
> --
> I doubt, therefore I might be.
>


.



Relevant Pages

  • Re: How Secure is ".Local?"
    ... > dozen servers and ~500 websites/public domains. ... Shadow DNS ... Is your DC on the Internet? ... >>It is not going to provide your zone info to anyone ...
    (microsoft.public.win2000.dns)
  • RE: New Forest - Old Domain - Plus DMZ - Help Please
    ... Make sure Windows XP client should use the AD DNS ... The Cert should match the name in Internet. ... New Forest - Old Domain - Plus DMZ - Help Please ... vast majority of our inside production equipment is 2003 servers and XP ...
    (microsoft.public.windows.server.migration)
  • Re: Active Directory and child DNS Zone
    ... > Our internal and external DNS domains are both the same - mycompany.com. ... > hosts our external domain and it only contains entries for our web servers ... >>> but the test bed isn't a true picture (no internet access to test VPN, ...
    (microsoft.public.windows.server.dns)
  • Re: DNS design questions
    ... We're a medium size college campus with about 10,000 users and the CIO wants to have DNS locally housed. ... only a hand full to a few dozen max "Internet servers" while ... how big of a security issue really is allowing the "external" DNS server pull a zone transfer from an internal one? ...
    (microsoft.public.windows.server.dns)
  • Re: How Secure is ".Local?"
    ... dozen servers and ~500 websites/public domains. ... I'm weighing the importance of split-brain DNS ... >It is not going to provide your zone info to anyone ... >on the Internet since local is NOT a zone in the ...
    (microsoft.public.win2000.dns)