Re: nslookup
- From: one3cap <one3cap@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 14 Aug 2007 20:30:00 -0700
The thing that is puzzling me it seems as is DNS is working properly ( i
might be wrong! ) Because on these clients that are having the issue for
example they try to go to http://triton/emr they get a page cannot be
displayed...... then i do my normal thing on the computer and try to:
ping triton and get "could not find host".... but if i do ping
triton.domain.local then i get "replies" and further \\triton =
"could not find" but \\triton.domain.local "works"..... then i go
to nslookup and this points to internal dns server and do a lookup for
triton it does find triton.domain.local with correct ip address this is
in my eyes telling me that the client is getting proper dns name
resolution..... i was thinking a WINS issue because of the netbios name it
was trying to resolve the name triton but the FQDN name of
triton.domain.local was working this is happening on mutiple names
and then the helpdesk guys were doing a ipconfig /flushdns and then
everything was working again which REALLY puzzled me because the nslookup
results were exactly the same after the flushdns command. i might be wrong
looking at this from a WINS side but the \\triton not working but
the \\triton.domain.local working was telling me dns is fine but then
the whole flushdns fixing it confused me.
"Herb Martin" wrote:
.
"one3cap" <one3cap@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F24B4A1E-D8D5-4244-A811-924EBBCD0E63@xxxxxxxxxxxxxxxx
this is a strange issue that just happened a few days ago it had been
working
fine for 1 year.
i have 20 remote sites and 1 main data center. 2 domain controllers in my
main site
172.29.3.4 dns/dc/dhcp/wins
172.29.3.19 dns/dc
windows server 2003 enterprise
all my sites connect via fast wan links to main data center. ones of those
servers are hosting dhcp successfully giving IP's to clients. All is good
excpet for many clients in my northern division. we have many web based
apps
that use servername/appname.
the problem is not all but many are getting "page cannot be displayed"
now
when i remote into these computers i look at dns on clients and both pri
and secondary dns is pointed to internal dns servers. i try to ping the
server by netbios name and get no reply but if i ping by FQDN i do get a
reply. what i have to do to fix the issue is do a ipconfig /flushdns and
all
is good but then i will get a call from the same client computer with the
same issue.
That implies the problem is in the DNS Client Cache but generally this
starts
with a sick DNS Server or Servers. You clear it and then things
(apparently)
work briefly which tends to imply ONE instead of all DNS servers are sick.
Check each of your DNS servers (configured on the clients) SPECIFICALLY.
Once you have such problems it is INSUFFICIENT to just do a default
NSLookup without checking each DNS server individually and specifically:
nslookup Server.Domain.Name IP.OfEach.DNS.Server
Clients cache NEGATIVE responses too, so if your DNS servers are "working"
but returning NOTHING then this might be part of the problem.
when i run nslookup i get the proper internal dns server and set type=a i
get an answer with ip for netbios name. i am puzzled as to what i causing
this
You need to work through each DNS server systematically -- most likely
Make sure you didn't do "Mutual Forwarding" on your DNS Servers, e.g.,
Forwarding: DNS1 -> DNS2 and DNS2 -> DNS1
- Follow-Ups:
- Re: nslookup
- From: Herb Martin
- Re: nslookup
- From: Ace Fekay [MVP]
- Re: nslookup
- References:
- Re: nslookup
- From: Herb Martin
- Re: nslookup
- Prev by Date: Re: DNS Errors 4004, 4007, 4015
- Next by Date: Re: nslookup
- Previous by thread: Re: nslookup
- Next by thread: Re: nslookup
- Index(es):
Relevant Pages
|
