Name | search
Click here to view Name news from 60+ newspapers.
Bookmark or Share- Local DNS not resolving host name but will resolve FQDNAt this point I noticed DNS was having problems. From the client I am not able to resolve the servers host name but I am able to hit it by FQDN: C:\Documents and Settings\Administrator>nslookup Default Server: sh-server.domain Address: 10.71.40.100 ^ sh-server *****unsuccessful when querying host name
- Can someone please explain Windows Service Principle Names (SPNs ...A Service Principal Name is a concept from Kerberos. It's an identifier for a particular service offered by a particular host within an authentication domain. The common form for SPNs is service class/fqdn@REALM (e.g. IMAP/[email protected]).
- windows - Resolve host name from IP address - Server FaultThis is the statement I wouldn't believe unless I see it myself ;) The explanation must be that nslookup uses only DNS protocol, but tracert uses the system name resolution library which uses DNS as a last resort, after WINS, NetBIOS, hosts file and so on were tried; however, in your example the name looks like DNS name.
- Find name of Active Directory domain controller - Server FaultFor a computer that is a member of a domain the Environment Variable LOGONSERVER contains the name of the DC that authenticated the current user. This is obviously not going to be all DC's in a multi-DC environment but if all you want is a quick way to find the name of a Domain Controller then from a command shell: set l
- DNS can't resolve hostname; nslookup can - Server FaultIn the end I found that IPv6 was causing the problems with the name resolution: on each DNS query the IPv6 DNS was queried rather than the IPv4 company DNS servers. After deactivating IPv6, you have to ipconfig /flushdns otherwise previously queried addresses may still not be resolved.
More
