DNS Parent Servers - Best Practice
I have 4 DNS Servers in my network.
(2) W2003 for Active Directory and (2) W2000 for public websites
I have registered as NS records at parent servers (to the Registry) the (2) W2000 for public websites
When I run www.dnsstuff.com I get a WARNING
FAIL: You have one or more missing (stealth) nameservers.
The following nameserver(s) are listed (at your nameservers) as nameservers for your domain,
but are not listed at the parent nameservers
--... list of my (2) W2003 for Active Directory
What is the best practice to declare as Primary/Secondary DNS at parent level? (Registry)
My AD DNS servers -or- the public ones? (and what issues are involved in each case that i should be aware for?)
(2) W2003 for Active Directory and (2) W2000 for public websites
I have registered as NS records at parent servers (to the Registry) the (2) W2000 for public websites
When I run www.dnsstuff.com I get a WARNING
FAIL: You have one or more missing (stealth) nameservers.
The following nameserver(s) are listed (at your nameservers) as nameservers for your domain,
but are not listed at the parent nameservers
--... list of my (2) W2003 for Active Directory
What is the best practice to declare as Primary/Secondary DNS at parent level? (Registry)
My AD DNS servers -or- the public ones? (and what issues are involved in each case that i should be aware for?)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks!
I think the issue you have mentioned are more likely a client config related ones. As you may be aware, if a client cannot see the right DNS servers (your AD ones) then there is a problem straight away in getting the user to authenticate. So should be the remote console access.
I think the issue you have mentioned are more likely a client config related ones. As you may be aware, if a client cannot see the right DNS servers (your AD ones) then there is a problem straight away in getting the user to authenticate. So should be the remote console access.
ASKER
I'll just wait for some other or similar opinion because...
I have had some issues (not all the time) -peculiar ones- like I'm not able to authenticate a sertain user to some domain computers or I'm not able to remote login with mcs console. I beleive this has to do something with how the 4 DNS must operate...in connection with the parent dns
You get (at least) 50% of the points, for your time spend for me, that I appreciate a lot.