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..??
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..??
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Natty Greg
Sure you can just keep an eye out for any unforeseen issues
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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..
TCP-IPv6.PNG
Listen-DNS-queries.PNG
TCP-IPv6.PNG
Listen-DNS-queries.PNG
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.
ASKER
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..?
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..?
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.
ASKER
My internal DNS is forwarded to the parent company ISP's so resolving is not the issue (foreign/external hosts).
Was there a follow-up question in that statement?
ASKER
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...
DNS-cmd.png
From cmd everything seems to be Ok....I'm getting positive results...?? Not From DNS manager...
DNS-cmd.png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.