Alright, I clearly do not understand the underlying mechanism for how AAM works.
I'm hoping that by pinging the list here, I either get a response, or distill
the information I do know into the answer. :)

I have a SharePoint Foundation server running on SPFDNSVR. I have a web
application on that server running on port 10000. The default name of the web
application and the default public URL for that same application are
http://spfdnsvr:10000/.

Now, I had our networking group reserve an IP for a VIP, DNS reserve a name, and
the VIP configured (address pointing to server name port 10000, SSL offloading,
etc.)

The new FQDN for the server *should* be https://foundation.mycompany.com.

I went into the AAM for that web application and added
http://foundation.mycompany.com Intranet
http://foundation.mycompany.com
https://foundation.mycompany.com Internet
https://foundation.mycompany.com

That didn't work. I even tried adding
<ip address of spfdnsvr> foundation.mycompany.com
...to my HOSTS file and that also did not work.

So I poked around and after some reading thought that perhaps what I wanted to
do wasn't add an AAM, but extend the application. So I extended the application
to http://foundation.mycompany.com (port 80) (I couldn't extend it to https
because I didn't have a certificate on the sharepoint server.)

That still didn't work with the VIP, but it DID work with the HOSTS file.

After reviewing all of this, I thought that maybe the problem was the port
number. Would the following solution be correct and/or at least moving in the
right direction?


1. Extend web application to http://foundation.mycompany.com (port 10001)

2. Change the load balancer to point
https://foundation.mycompany.com<http://foundation.mycompany.com> at port 10001
instead of 10000

Is there a good reference for all of this? I've got the MS Press Admin's
Companion and WROX's SP 2010 Administration books and both have about 2 pages
(total) talking about AAM.