I work as a consultant and every time I visit a client site with my "workgroup" computer I go nuts trying to access their infrastructure from websites to domain names. This is especially annoying with respect to SharePoint because clients often do not have Alternate Access Mappings (AAM) configured for the fully qualified domain names. You can get around this problem by adding entries to your hosts file located in C:WindowsSystem32driversetc but that gets a little tiresome. Today I was finally fed up with swapping out hosts files and decided to apply some of my newly found DNS prowess that I gained while building out a virtualized SharePoint farm on my laptop.
When I attempt to HTTP or RDP into a client machine while plugged into a client network I get a 404 or server not found response. A quick solution at some locations is to use the FQDN such as resource.corp.companyname.com or resource.local, but this is hit or miss especially with SharePoint.
The Previous Solution
Well normally I would handle this by either using the FQDN, updating my hosts file, or using the client’s VPN. The VPN adapters will, more often than not, provide their own DNS allowing you to quickly and easily access corporate resources. The downside of using the VPN is, of course, the unpredictability and, in my case, incompatibility of the VPN client with a 64 bit OS.
Open your control panel, network connections and select your active network connection (for that client).
In the network configuration screens right mouse key on your active network connection and choose properties.
In the connection properties window select the Internet Protocol Version 4 (TCP/IPv4) and select properties.
In the properties window of the IPv4 protocol choose advanced
In the advanced window enter the DNS suffix for your current client site. This suffix should represent the DNS that you would use when accessing their datacenter hosted servers, keep in mind this might be different from the DNS suffix that you might use for workstations (ergo don’t rely on ipconfig /all).
Rating: 10.0/10 (1 vote cast)
Rating: 0 (from 0 votes)
Consultant DNS and the FQDN, 10.0 out of 10 based on 1 rating
Ulysses Ludwig is a SharePoint architect with over 16 years in the IT and computer industry. Ulysses' primary focus is SharePoint but he dabbles in the latest web technologies and likes to develop software in his spare time.