localhost is a FQDN. On most computers, it translates to 127.0. 0.1 in IPv4 or ::1 in IPv6.
Type "ipconfig" and press "Enter." This displays the IP address for your Windows server. Use this IP address to view the fully qualified domain name of the server.
Workgroup computers don't have an FQDN unless you specifically configure them to have one. They have only a NetBIOS (single label) name. Also, don't confuse the Primary DNS suffix with the DNS suffix search list as assigned by DHCP because they're two different things.
NOTE: This solution only works when targeting the .NET 2.0 (and newer) frameworks.
using System;
using System.Net;
using System.Net.NetworkInformation;
//...
public static string GetFQDN()
{
string domainName = IPGlobalProperties.GetIPGlobalProperties().DomainName;
string hostName = Dns.GetHostName();
domainName = "." + domainName;
if(!hostName.EndsWith(domainName)) // if hostname does not already include domain name
{
hostName += domainName; // add the domain name part
}
return hostName; // return the fully qualified name
}
UPDATE
Since a lot of people have commented that Sam's Answer is more concise I've decided to add some comments to the answer.
The most important thing to note is that the code I gave is not equivalent to the following code:
Dns.GetHostEntry("LocalHost").HostName
While in the general case when the machine is networked and part of a domain, both methods will generally produce the same result, in other scenarios the results will differ.
A scenario where the output will be different is when the machine is not part of a domain. In this case, the Dns.GetHostEntry("LocalHost").HostName
will return localhost
while the GetFQDN()
method above will return the NETBIOS name of the host.
This distinction is important when the purpose of finding the machine FQDN is to log information, or generate a report. Most of the time I've used this method in logs or reports that are subsequently used to map information back to a specific machine. If the machines are not networked, the localhost
identifier is useless, whereas the name gives the needed information.
So ultimately it's up to each user which method is better suited for their application, depending on what result they need. But to say that this answer is wrong for not being concise enough is superficial at best.
See an example where the output will be different: http://ideone.com/q4S4I0
A slight simplification of Miky D's code
public static string GetLocalhostFqdn()
{
var ipProperties = IPGlobalProperties.GetIPGlobalProperties();
return string.Format("{0}.{1}", ipProperties.HostName, ipProperties.DomainName);
}
This is covered by this article. This technique is more brief than the accepted answer and probably more reliable than the next most-voted answer. Note that as far as I understand, this doesn't use NetBIOS names, so it should be suitable for Internet use.
Dns.GetHostEntry("LocalHost").HostName
Dns.GetHostByName("LocalHost").HostName
Here it is in PowerShell, for the heck of it:
$ipProperties = [System.Net.NetworkInformation.IPGlobalProperties]::GetIPGlobalProperties()
"{0}.{1}" -f $ipProperties.HostName, $ipProperties.DomainName
And for Framework 1.1 is as simple as this:
System.Net.Dns.GetHostByName("localhost").HostName
And then remove the machine NETBIOS name to retrieve only the domainName
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With