Re: DNS Forward lookup problem - now having problems with a period (.)
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Mon, 15 Aug 2005 19:21:09 -0500
> 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!
There is an implied period there whether you put it in physically
or not -- some tools would require it be manually present (manual
zone files, nslookup) to be 'official' but the MMC usually is usually
DWIM (do what I mean) and gets it right.
The zone for AD needs to be dynamic and EVERY machine for the
domain needs to be using (this) INTERNAL DNS servers SOLELY.
Chances are you have some that are still pointing at the lost DNS
server (maybe even the DC itself.)
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 /server:DC-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: ]
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
"pbrill1" <pbrill1@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A66EA850-2458-4BDB-9C3D-BEDC44869569@xxxxxxxxxxxxxxxx
> 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
.
- References:
- Prev by Date: DNS Forward lookup problem - now having problems with a period (.)
- Next by Date: DNS not doing recursive lookups
- Previous by thread: DNS Forward lookup problem - now having problems with a period (.)
- Next by thread: Re: DNS Forward lookup problem - now having problems with a period (.)
- Index(es):
Relevant Pages
|
Loading
