ping cannot resolve, but dig and nslookup work.

Is your DNS server on 192.168.30.1 set up as the primary for the zone? I don't see an authority section in the dig response. (For a small network, there tends to be one primary forward zone, and one reverse zone.)

How many DNS servers are registered on and listed on the client? (Should be one, until and unless you have a secondary DNS server that's mirroring the current contents of your 192.168.30.1 DNS server.)

What do the following return?
+dig -x 192.168.30.1+
+dig -x 192.168.30.2+
+ping 192.168.30.2+

I also have this exact same Problem with SL. It comes and goes. Usually when a dns entry doesn't exist but then gets created.

It's almost like the dsc flush's valid lookups but holds onto invalid ones for some time.

Any answers

Message was edited by: Mowat22

Any answers to what? In all seriousness and without intending any snark here, +I also have this exact same Problem with SL. It comes and goes. Usually when a dns entry doesn't exist but then gets created.+ is not enough for me to build a specific response around.

Buggy DNS configurations or slow DNS resolutions can cause problems for the local site, and (depending on the particular IP addresses and DNS configuration in use) can cause problems Internet-wide.

If you don't know how to configure DNS, then you're going to have to read or experiment or attend classes or otherwise learn more (whatever works best for you), or you're going to have to call in somebody that does know from DNS, or you can out-source your DNS configuration or management, or (if you want to continue discussions here) we're going to need rather more detail about your current network configuration (firewall(s), any use of NAT, general wiring, router(s), etc) and around the DNS configuration.

Same problem here. It only happens when a new DNS entry is created (on my OS X server nonetheless...). When I go to non-Mac (linux or M$sft) both ping and nslookup work fine. Sounds like a bug.

One sidenote... When I log into the OSX server which is running DNS and I try nslookup and ping they both work. It's only on our Mac client machines that we see this issue.

Hello!
Strange network problem. dig and nslookup work, but can't ping host. Only reboot help and sometime dscacheutil -flushcache.

I had the same problem on my installation.

I have solved this when I remove the "localhost" (127.0.0.1) which was listed as forwarder in my DNS configuration of Mac OS X server. It's logical but the question is: "Is it normal that localhost is listed by default?"

For a local DNS configuration where you are running your own DNS server.... The NIC-level DNS setting points to the local DNS server (which can be localhost, if you're looking at the NIC directly on the local DNS box), and (only) the DNS server points to the forwarder; to the ISP DNS server(s).

The local boxes and their local NICs (other than via the DNS server(s) you're running) do not point to the ISP.

[Establishing A DNS Server On Snow Leopard|http://labs.hoffmanlabs.com/node/1436]

I had a similar problem, but I solved it! The main reason in my case is that the DNS search order was reversed. I use two dns servers, the primary dns is for my intra network and the secondary dns is for the extra network.

When I run the following command:

$ping my.intra.server

the secondary dns responded, so I removed the secondary dns entry from /etc/resolve.conf then it worked very well.