Strange DNS resolving behavior

[Barry Margolin]

In article <c660ti$h44$1 at sf1.isc.org>,
 "John Manly" <jwmanly at amherst.edu> wrote:

> Greetings, all.  I'm experiencing a strange problem with DNS resolving
> that I'm hoping someone can shed some light on.  A vendor that we work
> with has set up a DNS name in their domain,
> "amherst.publishingconcepts.com" as an A record with an IP address of
> 12.156.3.83.  However, my site's DNS servers (and one other ISP's DNS
> servers that I can find) for some reason cannot resolve this address.
> But every other DNS server that I've tried querying can resolve the
> address.  Further, the problem appears to be specific to this particular
> name -- other A records in the same domain (such as
> www.publishingconcepts.com or tigernet.publishingconcepts.com) resolve
> properly.  I have no idea where to start looking for a solution (or even
> an explanation of this.)

Try dumping your server's cache.

Also, get in the habit of using "dig" rather than "nslookup" when 
troubleshooting DNS.

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***