Search results
Results From The WOW.Com Content Network
- If I run nslookup from a client joined to the domain this times out twice before giving the correct result. I enabled the debug option to troubleshoot and I noticed a strange behaviour: when resolving nslookup appends the domain name als o to fully qualified names, and this result times out because there is no such dns record. Example:
DNS use - Root hints, no forwards setup, root hints are updated, recently upgrade DC with Windows 2008 R2, how can ...
Hi We have a Windows 2012 server running AD and DNS. Something really weird happened, Simple and Recursive qurey ...
Hello, I have one DC server on Windows 2008 Server and on the same machine is DNS server. I turn off firewall and ...
Greetings, I have a network of 50 PCs running Windows XP SP3, joined to a Domain (Windows 2008 R2 DC), with ...
United States (English) Brasil (Português) Česko (Čeština) Deutschland (Deutsch) España (Español) France (Français) Indonesia (Bahasa) Italia (Italiano ...
To have external domain (google,tahoo,cisco etc) name resolution, you need to have public DNS IP configured on DNS server's forwarder to query the ISP dns server for external domain name resolution like google.com,yahoo.com. The public dns address would be provided by your ISP, it has to be configured on dns server which might be running on ...
Hi All, having an issue with the NSlookup. For client PC, first two lookup always time out before getting an ip ...
Hi, I want to use Domain Security with a partner and I added multiple domains to the TLSSendDomainSecureList. Let's ...
Windows Server TechCenter. Sign in. United States (English)