DNS and Win 2012 R2

While I finished with promoting Active Directory Services on Win 2012 R2 when I started working on DNS I noticed constant issues with nslookup (unknown default server).When I used cmd and ran nslookup I was fine...after reading some articles I created new pointer within reverse lookup zone..did not solve the issue...
What I did within DNS interface tab I made modification so it listens only to the following IP address which is IPv4 and don't listen to IPv6.Now I'm not getting any "unknown" issues....Can I resolve my dilemma in that way..??
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
To resolve foreign/external hosts,you either need root hints or a forwarded to your ISP's DOS server.  best is to use root hints nd ensure configure your firewall to allow TOP and UDP  ports 53.
Natty GregIn Theory (IT)Commented:
Sure you can just keep an eye out for any unforeseen issues
Cliff GaliherCommented:
I cannot recommend your approach. Windows increasingly depends on IPv6 and you will have issues, if not now, down the road. As far as the unknown server, that isn't an error. It is just a reverse lookup failing, which is completely normal in an environment that is using IPv6 autodiscovery. It won't hurt your performance. It is not even an error in the traditional sense. Simply ignore it. Or fully deploy IPv6 in a managed way in your environment... which takes a ton of planning to execute properly. Nothing wrong with either choice. Both are far better than disabling DNS on IPv6.
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

mirekgAuthor Commented:
I use both protocols IPv4 and IPv6 and both they are enabled on my new DC server.The only thing I changed is that the server DNS only listen queries of defined IP....Look at the pictures..
Cliff GaliherCommented:
Doesn't change my answer. By disabling core services' use of IPv6, you get the same net effect that you would if you disabled IPv6 itself. It is akin to a city planner saying "we didn't tear up the road, it is still there. We only put up detour signs!" Cars aren't on the road either way. Maybe a few bicyclists still ride on it. You suffer similar negative impacts. All for a cosmetic issue. It isn't a course of action I'd recommend.
mirekgAuthor Commented:
Ok so since my environment is using IPv4  I'm assuming those errors are not critical and I can totally ignore them....
I thought reverse DNS look up will resolve my dilemma..Why when I run nslookup from cmd it works fine??
When I run nslookup from DNS default server unknown..?
Cliff GaliherCommented:
As I've said, that can bee ignored. And yes, you can make the servers "known" with properly configured rDNS. But not doing so isn't a detriment.
mirekgAuthor Commented:
My internal DNS is forwarded to the parent company ISP's so resolving is not the issue (foreign/external hosts).
Cliff GaliherCommented:
Was there a follow-up question in that statement?
mirekgAuthor Commented:
Last question with picture..Why I'm getting two different results between nslookup???
From cmd everything seems to be Ok....I'm getting positive results...?? Not From DNS manager...
Cliff GaliherCommented:
Both are valid responses. The first one is defaulting to IPv4 and there is a valid rDNS record, thus the name is returned. The second is defaulting to IPv6 and there is apparently no rDNS record for that IPv6 address so "unknown" is returned. Neither respnde will cause issues in normal operations.

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
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
Windows Server 2012

From novice to tech pro — start learning today.