DNS Forward lookup problem - now having problems with a period (.)

Tech-Archive recommends: Fix windows errors by optimizing your registry



Recently, we had a DNS server go down, and in the process, the forward lookup
zone was deleted. We are a relatively small shop, so we were able to
recreate the forward lookup zone on our AD-integrated DNS Server (which also
holds all 5 FSMO roles), by looking at the reverse lookup zone entries.

the forward lookup zone was recreated to look something like this:
company.com

After this was done, we have had sporadic problems on our network. I am
wondering if I should have created our forward lookup zone as " company.com.
" (with a period after the .com )

Any assistance would be greatly appreciated!

Additional notes to assist:

I ran the "netdiag /debug" utility, and found NUMEROUS errors that are all
similar. One section looks as follows:
***************************************************
CHECK NAME DomainDnsZones.homeruninn.net. on DNS server 10.0.0.9
***************************************************
The record is different on DNS server '10.0.0.9'.
DNS server has more than one entries for htisname, usually this means that
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '10.0.0.9', no need to re-register.
-------------------------------------------
The record on you r DC is
DNS Name = Domain DnsZones.homeruninn.net.
DNS Data =
A 10.0.0.9

The record on DNS server 10.0.0.9 is:
DNS Name = DomanDnsZones.homeruninn.net
DNS Data =
A 10.0.0.9
A 10.0.2.3

(ALSO: Again, we are using Windows 2003 AD-Integrated DNS.
The 10.0.0.9 server holds all the FSMO roles
the 10.0.2.3 server is a remote server; it does not seem to be able to
replicate the forward lookup zone

I'm just not sure how to best resolve the situation of
company.com
vs.
company.com.

SUGGESTIONS TO RESOLVE THIS PROBLEM WOULD BE GREATLY APPRECIATED!

--
pbrill1
.



Relevant Pages

  • Re: DNS Forward lookup problem - now having problems with a period (.)
    ... > we were able to recreate the forward lookup zone on our AD-integrated ... > DNS Server, ... If you post the output from netdiag /test:dns /v from both DCs and run ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Forward lookup problem - now having problems with a period (.)
    ... we have had sporadic problems on our network. ... Chances are you have some that are still pointing at the lost DNS ... If you have more than one Domain, every DNS server must ... > recreate the forward lookup zone on our AD-integrated DNS Server (which ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Forward lookup problem - now having problems with a period
    ... Thanks, both Herb and Kevin, for your input - the tests have been very ... temporarily got the computers in the remote area to work. ... Should I remove the dupliate forward lookup zone from the remote DC? ... >> The record is different on DNS server '10.0.0.9'. ...
    (microsoft.public.windows.server.dns)
  • Re: A Reverse Lookup Zone is necessary?
    ... Unfortunately I do not know what I should add as a Reverse ... The Server is Windows 2000 not Windows 2003. ... that is the Gateway and my DNS Server is 192.168.2.34. ... >> to make a new Reverse Lookup zone for my situation so I didn't touch ...
    (microsoft.public.win2000.dns)
  • Re: AD Replication: What Does "Fully Routed" Mean?
    ... >> resolving the various warnings and errors... ... Each domain has a DNS server that has a forward lookup zone, ...
    (microsoft.public.win2000.active_directory)