DNS Configure Two (2) or more domains in the same server

[jgutierrez]

Hi, this could be very frustrating for the rest of us. I am running OS X 10.3.8 Server with one domain and everything works fine. We only have one ip address. I need to configure a second domain with the same ip address, and probably, sometime later a third domain, with the same ip address too. Right now there is a zone with its records and a reverse file configured for this domain. How a second domain has to be configured? I look for this and did not find any help how exactly this second domain has to be configured. Any help, address, mail is very welcome. Thanks

[ghostman]

It really depends on what the server is doing.

If you are using only one IP address, you can only have one reverse for the server. This would cause problems with mail serving (many ISPs will reject email that originates from a server that has mismatching forward and reverse records). Web serving is another thing – configure Apache to listen for virtual domain by name. It also depends on whether your server is authoritative or not.

If the reverse is not necessary, then create a new zone and add a record that is an alias (CNAME record) to your original DNS entry. If you do the new zone from Server Admin, the program won’t let you create a reverse for a CNAME.

If you need the reverse to match, your best bet is to add a virtual IP (aka Multihoming) for each domain.

[afterhours]

If I wish to run two or more public sites with SSL certs for each one (shopping carts or priviledged content), do I not still need to set the server up for multihoming?

If so, obviously we’ll set up our DNS properly, but is multihoming on OSXS (Tiger) the same as with OS 10.4 Client (replicate a Network preference with the new static IP information for the second IP)?

And if this is the case, do I need to do anything with Apache settings or does its default of wildcarding listening over any IP for that machine take care of serving (provided I install the public cert properly)?

(No, I do not wish to install a self-signed cert… too many chuckleheads would freak about any unexpected dialog or warning onscreen. KISS.)

Has anyone written up a white paper on all of the steps to install a cert in Tiger Server yet? Information seems piecemeal at best — but I’m uncertain if my searches of the kb here and on Apple’s site exhausted the most likely resources.

[afterhours]

[QUOTE BY= afterhours] If I wish to run two or more public sites with SSL certs for each one (shopping carts or priviledged content), do I not still need to set the server up for multihoming?

If so, obviously we’ll set up our DNS properly, but is multihoming on OSXS (Tiger) the same as with OS 10.4 Client (replicate a Network preference with the new static IP information for the second IP)?

And if this is the case, do I need to do anything with Apache settings or does its default of wildcarding listening over any IP for that machine take care of serving (provided I install the public cert properly)?

(No, I do not wish to install a self-signed cert… too many chuckleheads would freak about any unexpected dialog or warning onscreen. KISS.)

Has anyone written up a white paper on all of the steps to install a cert in Tiger Server yet? Information seems piecemeal at best — but I’m uncertain if my searches of the kb here and on Apple’s site exhausted the most likely resources.[/QUOTE]

I think I’ve answered some of my own questions. Yes, multihoming seems to work with OSXS just peachy. Generating the cert seemed to work as well via the GUI as through the old CLI method. Josh — do you want a short whitepaper on this?

[Author]

Posts