Re: Brainteaser for you DNS wizards
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Thu, 13 Apr 2006 21:55:42 -0500
"DaylightLifter" <DaylightLifter.2684fw@xxxxxxxxxxxxx> wrote in message
news:DaylightLifter.2684fw@xxxxxxxxxxxxxxxx
I am new to the company and I have been tasked with solving a rather
baffling problem. Here is the problem, and please forgive me if I am
giving to much information.
Most people give to little info or their reports are imprecise
in their report. (The secret to troubleshooting is simplication
and being VERY explicit.)
Also putting the problem earlier in your message usually helps:
The problem is that every so often several of our workstations DNS
tables gets corrupted and is unable to resolve anything in house. It
gets the DNS address of our ISP servers.
A VERY common error of configuration is usually responsible
for this.
You likely have (some) stations configured with BOTH the
Internal and External DNS servers on the stations NIC->IP
Properties.
This is never going to be reliable as stations tend to "latch
onto" one of the DNS servers but clients need to be sure to
contact the DNS server which can resolve ALL INTERNAL
(and external) address they will need.
I have to flush the DNS in
order to correct the problem. It is a random event. We have the Box
checked on the DNS server to stop poisoning but this hasnt helped
either. Any ideas?
Check the NICs on each affective client and configure
STRICTLY the (internal) DNS Server (set) which can
resolve ALL names the clients will need.
Clients assume that every DNS server can find ALL names
and that whatever the DNS server finds -- or does NOT find
-- is the correct answer.
We have a small office network (30+ workstations). We have one DC
server running active directory on Windows 2000 server with active
directory. It is also our DNS and DHCP server. We use the DNS service
to resolve a couple of inhouse names. One of them is our mail server.
Our mail server is a windows 2000 proffessional workstation running
Novells Netmail XE mail server. We have a record setup on our DNS
server to resolve the name Mail to the mail server. We use the name
Mail to access the mail server via Thunderbird client and through a web
browser.
Now here is where it gets a little wierd. The DHCP server issues the IP
address of the inhouse DNS server to each of the workstations for DNS
services. It is the only DNS address it issues. However, There are no
forwarders set in the DNS settings on the server. The only other DNS
settings are the static IP addresses that are configured, on the
servers TCP/IP network settings.
Check the clients anyway -- since manual settings on the
client OVERRIDE anything issued by the DHCP server
EVEN WHEN the client accepts an IP address from DHCP.
If this is NOT the issue, then post the UNMODIFIED output
from an affected client's "Ipconfig /all" (paste TEXT, don't
use a graphic, and please don't type in or modify the output,
as we want to see exactly what the client shows.)
Also give us the IP of the correct DNS server (set) that should
be in use by clients.
Check hosts files to see what is present there.
(Should generally be nearly empty unless you are running
certain kinds of malware protection OR have already been
infected by malware viruses or trojans. In any case you should
be able to account for any hosts file entries.)
%systemroot%\system32\drivers\etc\hosts
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
.
- References:
- Brainteaser for you DNS wizards
- From: DaylightLifter
- Brainteaser for you DNS wizards
- Prev by Date: Re: DNS Error event 113
- Next by Date: Re: Child Domains
- Previous by thread: Brainteaser for you DNS wizards
- Next by thread: Re: DNS problem with 2003 AD and XP workstations
- Index(es):
Relevant Pages
|
