nslookup not working?

Hello I was wondering if I have a problem with my AD/DNS servers. I used to use the nslookup command to figure out ip to hostnames but now it's not working. I'm not sure when it stopped. I have two servers that are both DCs and DNS servers. When I open the DNS consoles I see the DNS entries for ip addresses in my domain. when I type nslookup I get logged into my primary DNS server. When I go to look up an ip address it always comes back saying that it can't find the address followed by a message saying non-existent domain. any ideas where to start looking to resolve this?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I'd suggest restarting the DNS server service on both DCs and check the DNS event log and system logs for errors when they're stopped and started.
Darius GhassemCommented:
You need to create a Reverse Lookup zone.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Abhay PujariCommented:
do you checked start of authority and name servers tab? Is it marked with "*". if yes, then remove it and add the same again. Restart DNS server service and check again.
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Abhay PujariCommented:
Is it AD integrated?
I second the Reverse Lookup zone, and make sure your DNS-Servers are registered with correct PTR records.
Well, there are two factors involved for that to work:
1) Be sure you are setting your record type for lookups in NSLOOKUP - use the "set type = PTR" (or whatever record type you want for that matter) before trying to lookup PTR records to resolve IPs to names.
2) You need to be trying to resolve IPs that have an existing reverse lookup zone in DNS for the server to respond with a name, as mentioned above. Without that, there is no zone for the host to register a PTR record in even via dynamic registration.
IF both of those are there, you should be able to use NSLOOKUP to perform reverse lookups for your IPs.
Abhay PujariCommented:
any update?
jbla9028Author Commented:
there was a problem with my reverse lookup zone. thanks. everyone
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.