DNS NSLOOKUP FAILURE

I am getting errors in the event log that say that the dns has recieved a
packet addressed to itself. I have 2 DNS servers and each one lists the other
as the primary, and itself as the secondary dns server. DNS across the
network seems to work fine, but when I do an NSlookup I get a message like
this:

NSLOOKUP IBM.com

SERVERNAME Unknown for 192.168.0.235 (the DNS server)

NON autorative answer

IBM.COM 64.22.18.135 (or whatever)

Any idea what is causing this?

Note: the A records and the SA records for both DNS servers are in the DNS
tables and are correct.
.

Relevant Pages

  • Re: DNS Issue
    ... I have two forwarders - my ISP's DNS servers. ... When you say you used NSLookup are you doing ... Internal DNS clients must use STRICTLY the INTERNAL ...
    (microsoft.public.windows.server.dns)
  • Re: Network share question
    ... >> I have made a check of the cables and seen nothing abnormal. ... > prove the DNS Servers are setup correctly. ... >> No problem at level of ping or and the name resolution is good. ... > nslookup hn016.Crelan.be 10.1.6.25 ...
    (microsoft.public.win2000.networking)
  • Re: nslookup strange return
    ... nslookup appends the Primary DNS suffix first, ... firewall and same DNS servers, the response is correct. ... this fit with the Wildcard record you mention? ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Issue
    ... I have two forwarders - my ISP's DNS servers. ... When you say you used NSLookup are you doing ... Internal DNS clients must use STRICTLY the INTERNAL ...
    (microsoft.public.windows.server.dns)
  • Re: Primary/Secondary DNS Issue
    ... zone transfer is allowed only between the two DNS servers using the name of ... I'm actually running the NSLOOKUP ... Which fails and said query refused. ...
    (microsoft.public.windows.server.dns)