|
Question : nslookup producing odd results
|
|
i have added a domain controller to an existing domain, and have also configured it as AD integrated DNS server. when i startup nslookup, the dns server listed is forestdnszones.domainname.local and will not resolve any names. if i exit, restart nslookup, i get domaindnszones.domainname.local and it will resolve a name. lastly, if i start nslookup again, i now get dnsserver.domainname.local(which is what i expected all along) and that also resolves names. the other DC servers do not do this.
additional info: the dns server in the network connections panel is set to the local machine. I am getting a 4515 informational warning in the event log but that has never been a problem prior.(I mention this because i dont know if they are related).
i cant seem to find any similar situations on the microsoft page or here in experts exchange(or at least i dont know the best way to search for this). any ideas?
|
Answer : nslookup producing odd results
|
|
PAQed with points refunded (250)
Computer101 EE Admin
|
|
|
|