Yes I can still ping the DNS server while it stops working.
I didn't try NSLOOKUP ... I wilol try this when the problem happens again and will come back.
Also I will check the event log
Main Topics
Browse All TopicsHi Experts,
We have a windows 2003 DNS Server (Not AD integrated)... non-secure update enabled. All the client systems pointing to that DNS using DHCP options.
Now the problem is the clients can ping a system using FQDN most of the times and sometimes they can't.
When it stops working ipconfig /flushdns don't make any differrence.
After doing a repair in network connection it starts working.
Please suggest what could be the possible cause of this problem?
Many Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
When I try to ping - Fails
=========================
Ping request could not find host host.domain.local. Please check the name and try again.
NSLOOKUP - Success
=========================
C:\>nslookup
Default Server: dns.domain.local
Address: 10.10.10.10
> host.domain.local
Server: dns.domain.local
Address: 10.14.98.21
Name: host.domain.local
Address: 10.10.10.10
PING DNS IP - successful
=========================
C:\ping 10.10.10.10
Pinging 10.10.10.10 with 32 bytes of data:
Reply from 10.10.10.10: bytes=32 time<1ms TTL=125
Reply from 10.10.10.10: bytes=32 time<1ms TTL=125
Reply from 10.10.10.10: bytes=32 time<1ms TTL=125
Reply from 10.10.10.10: bytes=32 time<1ms TTL=125
Ping statistics for 10.10.10.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Yes this is from the client
nslookup succeeds in resoving the address but pinging the host by fqdn fails where pinging by ip succeeds - Thats correct !
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : host1
Primary Dns Suffix . . . . . . . : domain-a.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain-a.local
domain-b.local
domain-c.local
domain-d.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : domain-a.local
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
Physical Address. . . . . . . . . : ##-##-##-##-##-##
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.10.10.12
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 10.12.24.1
DHCP Server . . . . . . . . . . . : 11.11.11.11
DNS Servers . . . . . . . . . . . : 10.10.10.10
13.13.13.13
Primary WINS Server . . . . . . . : 11.11.11.11
Secondary WINS Server . . . . . . : 12.12.12.12
Lease Obtained. . . . . . . . . . : 21 March 2007 3:03:20 PM
Lease Expires . . . . . . . . . . : 21 March 2007 7:03:20 PM
C:\>
Are these other addresses valid?
DNS Servers . . . . . . . . . . . : 10.10.10.10
13.13.13.13
Primary WINS Server . . . . . . . : 11.11.11.11
Secondary WINS Server . . . . . . : 12.12.12.12
Even with a rather large subnet of 255.255.248.0 both wins servers would be on different networks.
If you don't have these servers, I'd remove them from the DHCP config. You don't HAVE to have a secondary DNS or any wins servers.
The DHCP server seems on a different network as well - which can be done with a helper address - but are these addresses greeked or is this what you're serving up from 11.11.11.11?
Have you checked basic stuff like speed/duplex mismatches, extraeneous host file entries, etc?
How about the event logs?
You (on the network admin) would have to look on the switch and the host to check what speed / duplex had been negotiated. If in doubt you can set both explicitly.
The hosts file is in <system root>\system32\etc on the client and can contain ip/name entries that supercede DNS resolution. There could also be an LMHOSTS file that supercedes WINS resolution.
Check both event logs.
Speed is full duplex autonegotiated ... in client sire 100 mbps and in DNS server 1Gbps
There is no host or LMhost entries
No error or warning in server event log but Lots of dhcp warning messages in client side
Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 22/03/2007
Time: 9:33:58 AM
User: N/A
Computer: C4D3C2J
Description:
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 0013728F34C5. The following error occurred:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
For more information, see Help and Support Center at http://go.microsoft.com/fw
Data:
0000: 79 00 00 00 y...
Business Accounts
Answer for Membership
by: chicagoanPosted on 2007-03-20 at 10:37:49ID: 18758176
When is stops working, have you checked if there is basic connectivity to the DNS server?
Can you ping it? What happens when you query DNS on a client via NSLOOKUP?
What happens when you query the name server by running NSLOOUP on the name server host?
Anything in the event logs?