As per the title, I'm using 64-bit ultimate in a 2003 domain. Brand
new install and I've noticed that frequently (talking 3-4 times a day
here) the DNS service appear to suddenly stop being asked to perform
lookups. The service itself never appears hung or stopped, but
wireshark suddenly reports broadcast being used to look up hosts
instead of DNS.

As soon as I restart the DNS service, normal service resumes.

I've also installed the ISA client and it's the same operation. Trust
me, my network settings are correct

It's as simple as :

c:\ping testmachine
Ping request could not find host testmachine. Please check the name
and try again.

(wireshark shows broadcast)

c:\nslookup
Default Server: ourinternaldnsserver.x.x.x
Address: 10.40.x.x:53

testmachine
Server: ourinternaldnsserver.x.x.x
Address: 10.40.x.x:53

Name: testmachine.x.x.x
Address: 10.40.2.7

(wireshark shows proper DNS query and result as expected)

c:\ping testmachine
Ping request could not find host testmachine. Please check the name
and try again.

(wireshark shows broadcast for name lookup)
(restart DNS service)

c:\ping testmachine

Pinging testmachine.x.x.x [10.40.x.x with 32 bytes of data:

Reply from 10.40.x.x: bytes=32 time1ms TTL=255
(wireshark shows dns lookup, followed by icmp)
etc.

(Note that this isn't a DNS postfix issue, results are the same
whether the full domain name is specified or not). Also, by and large
the reason that broadcast don't return an answer is that I'm going
across routed nets, and also frequently to unix hosts.

Any ideas? It's enough to be annoying. Have been googling for a while,
no joy as yet

Thanks

AW

Further to this, as soon as the machine boots I have no network
connectivity. I set the dnscache service to manual instead of
automatic. And I've got it stopped 100% of the time. Now everything
works as it should. Anyone else getting this trouble might like to try
disabling that service as well.

This case is repeatable - I've done a fair bit of testing and stopping
dnscache appears to be the only sure-fire way of stopping this
problem.

Still no idea why it should occur however, so grateful for any
suggestions.

Cheers
AW

On 12 Apr, 10:59, "andreww" wrote:
As per the title, I'm using 64-bit ultimate in a 2003 domain. Brand
new install and I've noticed that frequently (talking 3-4 times a day
here) the DNS service appear to suddenly stop being asked to perform
lookups. The service itself never appears hung or stopped, but
wireshark suddenly reports broadcast being used to look up hosts
instead of DNS.

As soon as I restart the DNS service, normal service resumes.

I've also installed the ISA client and it's the same operation. Trust
me, my network settings are correct

It's as simple as :

c:\ping testmachine
Ping request could not find host testmachine. Please check the name
and try again.

(wireshark shows broadcast)

c:\nslookup
Default Server: ourinternaldnsserver.x.x.x
Address: 10.40.x.x:53

testmachine

Server: ourinternaldnsserver.x.x.x
Address: 10.40.x.x:53

Name: testmachine.x.x.x
Address: 10.40.2.7

(wireshark shows proper DNS query and result as expected)

c:\ping testmachine
Ping request could not find host testmachine. Please check the name
and try again.

(wireshark shows broadcast for name lookup)
(restart DNS service)

c:\ping testmachine

Pinging testmachine.x.x.x [10.40.x.x with 32 bytes of data:

Reply from 10.40.x.x: bytes=32 time1ms TTL=255
(wireshark shows dns lookup, followed by icmp)
etc.

(Note that this isn't a DNS postfix issue, results are the same
whether the full domain name is specified or not). Also, by and large
the reason that broadcast don't return an answer is that I'm going
across routed nets, and also frequently to unix hosts.

Any ideas? It's enough to be annoying. Have been googling for a while,
no joy as yet

Thanks

AW