DNS client suddenly stopps working

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

on some Windows2000 and WinXP clients in our Domain the DNS
client/resolver just stopps working. a reboot of the PC makes
it work again.
interestingly this happens only to our own domain! other domain
lookups (i.e. internet servers) still work!

our domain is intra.ourdomain.ch
-ping server1.intra.ourdomain.ch stopps working after some hours
of uptime: could not find host ...
-ping server1 still works (I think thats because of the Netbios resolver)
-ping www.otherdomain.com still works.
-with nslookup it works always, so it's not a server problem.
-putting the server into the hosts file would solve the problem,
but thats not the idea...

for Windows servers this is not a big deal, they can be resolved
over Netbios. but all other servers are not reachable anymore until
a reboot of the client is done.

any hints?
thanx
Domi

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

"Dominic Wyss" <news@doomi.ch> wrote in message
news:4176579c$0$330$4d4ef98e@read.news.ch.uu.net...
> on some Windows2000 and WinXP clients in our Domain the DNS
> client/resolver just stopps working. a reboot of the PC makes
> it work again.
> interestingly this happens only to our own domain! other domain
> lookups (i.e. internet servers) still work!

Classic symptom of someone setting BOTH an internal
and an external DNS server in the machine's client IP
properties (on the NIC\IP).

ONLY internal DNS servers should be used for internal
(especially domain) machines.

To resolve external names, the internal DNS servers
should forward (to the ISP or a firewall) to an external
resovling DNS server.

--
Herb Martin


>
> our domain is intra.ourdomain.ch
> -ping server1.intra.ourdomain.ch stopps working after some hours
> of uptime: could not find host ...
> -ping server1 still works (I think thats because of the Netbios resolver)
> -ping www.otherdomain.com still works.
> -with nslookup it works always, so it's not a server problem.
> -putting the server into the hosts file would solve the problem,
> but thats not the idea...
>
> for Windows servers this is not a big deal, they can be resolved
> over Netbios. but all other servers are not reachable anymore until
> a reboot of the client is done.
>
> any hints?
> thanx
> Domi

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

> Classic symptom of someone setting BOTH an internal
> and an external DNS server in the machine's client IP
does this mean that Windows is suddenly changing from
first to the secondary DNS server for resolving hosts?
whats the reason for switching?

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

"Dominic Wyss" <news@doomi.ch> wrote in message
news:4176ec99$0$325$4d4ef98e@read.news.ch.uu.net...
> > Classic symptom of someone setting BOTH an internal
> > and an external DNS server in the machine's client IP
> does this mean that Windows is suddenly changing from
> first to the secondary DNS server for resolving hosts?
> whats the reason for switching?

(correct) Server is busy or gets rebooted or some such

--
Herb Martin

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

HM> To resolve external names, the internal DNS servers should forward
HM> (to the ISP or a firewall) to an external resovling DNS server.

.... or just perform the query resolution themselves.

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

thanx for the hint. it seems that the affected hosts indeed
do have an external server as second DNS.

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Remove the external DNS server from ALL NIC/IP
properties (including servers) and add a forwarder
to your internal DNS servers (if needed.)

All clients will query internal servers which will
then either answer directly or query the external
names on behalf of the clients.

Remember that "servers" are clients too!

AD DNS
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

Restart NetLogon on any DC if you change any of the above that
affects a DC.

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.


--
Herb Martin


"Dominic Wyss" <news@doomi.ch> wrote in message
news:cl7n2b$3ui$1@atlas.ip-plus.net...
> thanx for the hint. it seems that the affected hosts indeed
> do have an external server as second DNS.
>
>