OpenSSH - libwrap error on Ubuntu 12.04

While attempting to install OpenSSH-Server on Ubuntu Server 12.04 I received the following libwrap0 error:

josh@test03:~$ sudo apt-get install openssh-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be install. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:
 
The following packages have unmet dependencies:
 openssh-server : Depends: libwrap0(>= 7.6-4~) but it is not installable
                      Recommends: ssh-import-id but it is not installable
E: Unable to correct problems, you have held broken packages.

The problem was resolved by running:

sudo apt-get clean
sudo rm -rf /var/lib/apt/lists/*
sudo rm -rf /var/lib/apt/lists/partial/*
sudo apt-get clean
sudo apt-get update
sudo apt-get upgrade

DirectAccess Certificate Binding Error

Problem:

I recently set up a single server DirectAccess box on Server 2012 R2.  I started having problems with clients not properly discovering the Network Location Server.  I logged on to the DirectAccess server and noticed the following on the Remote Access Management Console.

Specifically, the Network Location Server service reported an issue with Certificate Binding and Server Availability.

The specific error was:

The certificate binding for the network location server has been modified. Without the correct certificate, connectivity for DirectAccess clients located in the internal network will not work as expected.

Initially I thought there was something wrong with my DirectAccess certificate.  I also received an error when I checked the certificate in Infrastructure Setup.

The certificate subject name cannot be resolved to a valid IP address.

Solution:

The DNS entries that DirectAccess creates when it is set up were accidentally deleted in DNS by scavenging rules.

The entries that I had to add back were:

DirectAccess-NLS
DirectAccess-WebProbeHost
DirectAccess-CorpConnectivityHost

The CorpConnectivityHost entry had both "A" and "AAAA" records. The other two were just "A" records.

After adding these DNS entries, the errors went away.