Legacy Application with DNS Limitations

We deploy the real environment, you take the scenario-based labs on us. Hands-on, from anywhere, at any time.

Time required: 3 Hours


Resolve a static DNS issue between a legacy application server and a client connection.


Understanding how your system resolves DNS and in what order DNS queries are made will allow you to troubleshoot and resolve non-obvious communication issues in your environment.


When your shipping company purchased the warehouse in Kansas, they inherited a custom application for inventory control that was running on a very old version of Red Hat Linux Desktop (v9). The system that it was running on has failed. Fortunately, they were able to move the application to the new CentOS systems that you have been deploying.

Both the client and server application however are having issues. Each is hard coded to use a specific name to refer to the other. However, because other systems at the location are already all configured to interact with these new systems by their deployed host name, the existing names cannot be changed.

You will need to log in to both the client and server and create local configurations for each host so that they will be able to communicate using the old names provided below. Be sure to use the private address of each server when you start the lab and then verify that each can see the other. Check to verify that the DNS settings of each system will use local host entries before falling back to external DNS.

Server Name to Add -
Client Name to Add -

Share our Labs
Start Your Free Trial

We have the longest and most in depth courses about cloud and engineering topics on the web. All of our training content is included with every membership.