Re: DNS and active directory

"Jamie" <Jamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D2318462-9449-438C-85FC-3FFAD94BC888@xxxxxxxxxxxxxxxx
Thanks Herb,

This was not the issue, I decided to start from scratch and delete the dns
configuration on the server, I then created the forward zone again and
called
it the same name as the domain name,

What else WOULD you ever call it?

While you can have DNS zone with any name you
please, you MUST have a DYNAMIC DNS zone for
every Active Directory Domain.

If you don't have AD, you must have the DNS domain
name as a zone on your internal DNS servers that matches
the DNS domain name you machines use.

for some strange reason it started to
work immediately, this is the 4th time I had followed this process, I do
not
know why it should start working?

Likely this is happening through some accident, or
by chance. Stop flailing. (It's flailing to make changes
or do reinstalls, especially repetitively, without
understanding the problem.)

We WILL HELP you solve the real problem.

I still STRONGLY suspect that your problem is a MIXTURE
of internal AND EXTERNAL DNS on the client side.

This can result in intermittently correct and incorrect resolution.

Check the clients.

If you have AD, run DCDiag on every DC.

In any case, run NetDiag on each non-DC.

Send the output to text files (>name.txt) and search the file(s)
with a text editor to find FAIL, WARN, ERROR messages.

Fix, or post those output files.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

my concerns are it happening again, we shall see.

Thanks

Jamie
--
Jamie Campbell



"Herb Martin" wrote:

"Jamie" <Jamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D5E6BBC4-305A-4D9D-B128-6A9DD1C5BAD7@xxxxxxxxxxxxxxxx
I have a server problem and I think it is DNS related.

I can resolve external addresses, but I cannot resolve any internal
computers on my network, I think this is a dns misconfiguration.

at one stage none of the network clients could see the DC as they could
not
resolve its network address.

I am sure this is a simple fix, any ideas?

Yes, it is likely due to one of two VERY CLOSELY related
client DNS configuration problems.

On the CLIENT NIC->IP Properties you must use STRICTLY
the (internal) DNS Server (set) which can resolve ALL internal,
and external, names for the client.

You must NOT mix the "external" DNS into those settings.

DNS clients assumed that EVERY DNS server they use will
return ALL (and correct) names they query.

(Remember that DNS servers and DCs are also DNS clients
themselves.)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Thanks
--
Jamie Campbell






.

Relevant Pages

  • RE: exchange server cannot mount mailbox store
    ... What's the exact detailed DNS Events ... Type desired internal IP address of your SBS server. ... it will delete the reverse lookup zone if the zone no longer ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Event 4515 :another copy of zone has been found
    ... running on the old 2000 server. ... I then installed DNS on ... I seem to remember hearing that if you just delete/remove the zone it ... Container), the Configuration Partition, and the Schema Partition. ...
    (microsoft.public.windows.server.dns)
  • Re: Replication between parent child domains
    ... install dns before i run the dcpromo on the melbourne server. ... DNS server will forward any query it can't answer, Checks zone ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication between parent child domains
    ... DNS server will forward any query it can't answer, Checks zone ... DNS Servers) all queries will go to tld DNS server (including Internet ... Stub zones: Stub zones contain a read-only copy with specific records ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Redesign Issue
    ... -Using DNS console you can right-click the zone and export to a File, ... -To export a Zone and import that Zone in another DNS Server you need to use ... Create a child zone dallas on the DNS server in the child domain ...
    (microsoft.public.windows.server.dns)