On Thursday 11 August 2005 11:05 pm, Josh Welch wrote: > Dana S. Millaway wrote: > > A couple of clarifications for those who responded: > > > > 1. I have only 1 dns server within our system and it is running primary > > services only. It gets its dns information when necessary from another > > server upstream from us. > > > > 2. Our dns server IS NOT a windows box and I don't intend to put dns on > > a windoze box. :P > > > > A development in the saga: > > > > I tried pinging the family info server using just its hostname and got > > the server not found message. But when I pinged it with our domain name > > after it, it responded. So I specified the full name in the web address > > and voila!, it worked on both a mac and a win98 machine. I setup > > records for another of our app servers in the dns and it worked too. > > Yippee. > > > > So my remaining concern would be how to fill in the names of these app > > servers when I purchase my SSL certs. Do I use just the host name or > > the full name - ie - myserver.mydomain.k12.mn.us ? > > You should specify the full domain name in a certificate, so yes use > myserver.mydomain.k12.mn.us. > Yes, the primary thing you want to make sure you have correct is the "Common Name" in the SSL certificate as the "Common Name" field is what you will have in the URL for people to go to.... ie https://common-name.domain.com or whatever it is.