DNS & some confuse

[Guest]

dear All,

i have some confuse with My DNS.

i have here in My Network, 20 Clients, 1 DC, 1 ISA, 1Exchange server.

and the domain is in Native Mode.

My E-mail hosted in USA, in CIA host company.

To collect my E-mails from out side, i am uisng POP3 connector which connect
to the Host company and download the E-mails.

this is not big issue .

the main thing that, i configured my DNS to work Normally with the forward
lookup zone & reversed lookup zone .

all of my Clients, configured with the IP-address of the DNS.
=================================================

Now, my questions is :-

i am configured my DNS to work in LAN- internal.

what is the meaning of configuring External DNS to work with external.

i need to understand, please some advice

 

[Herb Martin]

dear All,

i have some confuse with My DNS.
i have here in My Network, 20 Clients, 1 DC, 1 ISA, 1Exchange server.
and the domain is in Native Mode.

Irrelevant to DNS or to clients -- only DCs care,
and the database capabilities of AD itself change
in native mode.

My E-mail hosted in USA, in CIA host company.
To collect my E-mails from out side, i am uisng POP3 connector which connect
to the Host company and download the E-mails.
this is not big issue .

the main thing that, i configured my DNS to work Normally with the forward
lookup zone & reversed lookup zone .
all of my Clients, configured with the IP-address of the DNS.
=================================================

Now, my questions is :-
i am configured my DNS to work in LAN- internal.
what is the meaning of configuring External DNS to work with external.

i need to understand, please some advice

Your question is not clear or not clearly stated so
let's just detail how your DNS SHOULD work:

Internal machines (all such) should be clients of the
INTERNAL DNS servers SOLELY. (Do not put
external DNS servers on any of the internal machine
NIC settings.)

In general, your internal DNS servers will FORWARD
to your ISP or your gateway/firewall (caching only)
DNS server.

Here's more....

DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /serverC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]