Hosting Multiple Mail Domains

Hi There:
I have some questions, will you please help me.
My Server is set
example.com
I need to set additional / Multiple E-Mail Domains, these need to be separated, like:
example1.com
example2.com
example3.com
For the E-Mail Client, what will be de In-Comming Mail Server and Out-Going / SMTP
mail.example1.com
mail.example2.com
mail.example3.com
or it will be "mail.example.com" for all 4 Domains.
I would like to say THANK YOU in advance

This is entirely possible, and supported by the Server Admin user interface for the mail server.
Start with the [Mac OS X Server Mail Services Administration Manual|http://images.apple.com/server/macosx/docs/MailService_Adminv10.6.pdf], page 73
Quoth the Book Of Mail:
A Mail Service Virtual Host
Virtual hosting is a method you can use to host more than one domain name on the same
computer and IP address, with overlapping mail user names.
For example, a mail server can receive mail transfer requests for two domains,
mail.example1.com and mail.example2.com, both of which resolve to the same IP
address. For mail.example1.com, the server delivers mail to “[email protected]”
to a user mailbox for “bob,” while it also delivers mail to “[email protected]” to
a different user mailbox. Virtual hosts are essentially the converse of local host aliases.
One subtlety here is that the domains sharing the same mail server and all co-resident on the IP address will all tend to have the same public host name listed as their MX (mail exchange) server of record in the public DNS. This so that forward and reverse DNS and MX server all line up for the mail server for all the domains involved.

Similar Messages

Hosting Multiple Mail Domains in SL server on a Mac Mini

So I have been trying to find out the answer to this question, and I keep getting conflicting information, and I am hoping someone here can help me solve this.
We are running two very small business with two different Domains (@company1 & @Company2) Each company has a website, and corporate email. All I want to do is bring all of this in-house onto one Mac Mini server. The calendars and contacts will be shared between the two principle owners of each company (my bosses) as they support each other in there individual business.
The Apple "Genius" says this is not possible, I believe and have been told by a few people and after reading posts on here that it is possible to have multiple domains on one Mac Mini Server. I would like to figure this out quickly as the companies have a need to move off the current email provider as fast as possible due to complications with iOS4 and the iPads.
Any Help from people who are doing this, or know it to be possible or impossible would be greatly appreciated!

This is entirely possible, and supported by the Server Admin user interface for the mail server.
Start with the [Mac OS X Server Mail Services Administration Manual|http://images.apple.com/server/macosx/docs/MailService_Adminv10.6.pdf], page 73
Quoth the Book Of Mail:
A Mail Service Virtual Host
Virtual hosting is a method you can use to host more than one domain name on the same
computer and IP address, with overlapping mail user names.
For example, a mail server can receive mail transfer requests for two domains,
mail.example1.com and mail.example2.com, both of which resolve to the same IP
address. For mail.example1.com, the server delivers mail to “[email protected]”
to a user mailbox for “bob,” while it also delivers mail to “[email protected]” to
a different user mailbox. Virtual hosts are essentially the converse of local host aliases.
One subtlety here is that the domains sharing the same mail server and all co-resident on the IP address will all tend to have the same public host name listed as their MX (mail exchange) server of record in the public DNS. This so that forward and reverse DNS and MX server all line up for the mail server for all the domains involved.

Multiple Mail Domains with multiple IP addresses

Hello,
I am attempting to configure a mail server with 3 domains and 3 distinct IP addresses. I am currently only working with 2 of the domains.
Mail sent to either domain is received by the accounts in both domains: if I send a message to [email protected], it goes to both that mailbox and the [email protected] mailbox. I have user accounts set up in WGM for both domains.
I'm sure I have something misconfigured, but the only instructions I can find for multiple domains assume virtual domains using only one IP address.
postconf -n
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps = proxy:unix:passwd.byname $alias_maps
luser_relay =
mail_owner = postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mapsrbldomains =
mydestination = $myhostname,localhost.$mydomain,localhost,mail.tomsheehan.com,tomsheehan.com,ma il.19north.com,19north.com
mydomain = tomsheehan.com
mydomain_fallback = localhost
myhostname = mail.tomsheehan.com
mynetworks = 127.0.0.1/32,66.216.189.129/32,66.216.189.133/32,66.216.189.134/32,tomsheehan.c om
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdclientrestrictions = permit_mynetworks rejectrblclient zen.spamhaus.org permit
smtpdpw_server_securityoptions = login
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtls_keyfile =
smtpduse_pwserver = yes
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains =
virtual_transport = virtual
Thanks in advance for any help I may receive!
Scott
iMac Core2Duo 2 GHz, iMac G4 700, iMac G4 800, iBook G3 900 Mac OS X (10.4.9)

Scott,
can you elaborate a bit on the final goal?
There is no need to use multiple IPs to run seperate domains. Virtual domains can handle this just fine.
You could run three different instances of postfix bound to different IPs and different configurations. (postfix -c configdir_touse start) Each config directory would have its own main.cf with the main parameters to be changed being "inet_interfaces", "myhostname" and "mydomains". However, unless you have a very specific need this is just an extra headache.
Alex

Hosting Multiple Web Domains

I have a WRT160N
In the DDNS configuration there is only a space to put one domain name. I have multiple domains hosted off the same web server. Is there a way to add other domains? i.e. comma deliminated or using semi colons, etc
Thanks,
Mike

A work around that works for the most part is to enter a host name in the DDNS section, save it, then replace it with another name and save it. As long as you do not get another dynamic IP....it works.
I guess I will use this work around until I rebuild my Linux router.
Regards
(Mod note: Edited for forum compliance.)

How do I host multiple domains on a single Messaging Server?

How do I host multiple domains on a single Messaging Server?
<p>
To host multiple domains on one Messaging Server, use the
mailAlternateAddress attribute. If you want to host two domains
(customer1.com and customer2.com) on your server mail1.domain.com,
make sure that:
The various domains (in DNS) point to the installed mail server
(you must have the MX records that
points mail for customer1.com to mail1.domain.com and
customer2.com to mail1.domain.com)
That each person receiving mail at customer1.com and
customer2.com has an appropriate mailAlternateAddress
attribute describing the appropriate email address. For
instance, John Doe can have an email address (i.e. the value
of the 'mail' attribute for the John Doe LDAP entry) of
[email protected] and receive his mail on
[email protected] (the value of the mailAlternateAddress
attribute)
With Messaging Server 3.5, mailAlternateAddress can take the
form of @mail1.domain.com. If jdoe's mailAlternateAddress is
set to @mail1.domain.com, mail sent to [email protected]
will be delivered to [email protected]

jaygatsby1123 wrote:
So what exactly am I doing with virtual hosts? There is a place for Aliases... What would I put in the "Aliases" box?
Any other host name that you want to resolve to the specified virtual host. It's quite literally an alias.
if you want www.example.com and www.example.org to end up at the same web site and you already have a virtual host — Apple refers to virtual hosts as sites — configured for www.example.com in Server.app, then you'd add www.example.org as an alias for the www.example.com virtual host (site).
Virtual hosts are implemented in a web server using some details of the HTTP or HTTPS protocol, and what the web browser (client) specified. The client gets handed an IP address or a domain name by the user, and the client then fetches the associated IP address for the target web server from the client's DNS services or local host database, and the client then connects to the IP address and passes over the text string that the user had requested — the IP address or domain name or even some local shortcut set up in the client system — via the HTTP or HTTPS protocol. The web server receives and processes this arriving text string from the client, and uses it to select which web site to render back to the web client. One subtle detail lurks here, too: the server's own DNS configuration really isn't involved in the selection of the virtual host.

Can you host multiple domain names on mobile me with iWeb '09?

Hi
Can anyone help, before I upgrade to iLife '09, I have a personal web domain name which I host on my mobileme account. My girlfriend now wants a website and I have bought her a domain name and want to use iWeb to design it but I can't seem to host multiple domains on iWeb '08, can you with iLife '09? Or will she have to buy her own mobile me account? Any help will be great!!!
Thanks

MobileMe -MME -is Apple's hosting service.
Domain Name System - DNS translates an understandable address like www.mywebsite.com into the IP address which is a number like 40:75:92:301.
Cname is a name of record in a database that records what domain name goes to what IP address.
IP address is just a unique number that identifies any device connected to the internet.
An FTP client is an application the uploads your files to a server using File Transfer Protocol.
I mainly use Web Site Maestro because it doesn't just upload the files but optimizes them first to remove all the unnecessary code that iWeb creates to allow your website to download at least 30% faster.
I also use Yummy FTP for sorting out and keeping track of my files on the server and uploading folders of images and music files along with their assets for flash presentations.
I have used Host Excellence for years because of the way they allow you to name your own root folder on the server and also their great tech support.
FTP and servers can be a bit confusing but, if you have a good hosting company, you can get by on very little knowledge and understanding. I do!
I couldn't agree more with you about the acronyms and jargon. The more people use them usually means the less they know. One of the most misused words is "domain". I tried to sort that one out here...
http://www.iwebformusicians.com/SearchEngines/Upload.html
Now I'm going FUH and ATNP.

Cisco Jabber client to support Multiple e-mail domains

Hi All,
Per the following link, CUCM an IM&Presence starts supporting multiple domains at version 10:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_0_1/delta/CUCM_BK_C206A718_00_cucm-new-and-changed-1001/CUCM_BK_C206A718_00_cucm-new-and-changed-1001_chapter_010.html#CUCM_RF_I31EA3AB_00
However, we have heard from Cisco that there is NO Jabber client that works with version 10 to support multiple email domains.
This may or not may be true.
Can someone who has connection with BU confirm this? If there is Jabber client that supports multiple email domains, what is the version and when is it going to be available?
Thanks,
Mustafa

Per-Olov
How are you dealing with this DA restriction?
Also, what are your comments about the use of Domain Alias vs. Domain with inetdomainbaseDN pointing to my organization? Which one was your choice?
Thanks,
Ivo

Virtual Mail Domains

10.4.10 Server.
I've set up virtual mail domains. Added email addresses to the shortnames list. When anyone sends an email to [email protected] it gets delivered to all hosted domains. So i get the same email in domain2.com.
Anyone know what's causing this?
cheers
Multiple Mac OS X (10.4.10)

Sydney, while you are waiting for a response, just a clarification on local DNS, MX, etc...
The MX record is only required for 'external' users, in order to discover where the responsible mail server is (because all they have to start from is a basic domain name, not a server hostname). In your LAN, your mail clients will already have this location as you put this into the sending/receiving field in the mail client - either as a hostname (which must be resolvable to the local server's IP in your local DNS) or directly as an IP address. So local DNS does not need an MX record if this scenario is applicable.
The hostname you put into your local mail client has no meaning to the mail server - it purely resolves to an IP address and then your client 'drops' that hostname and contacts the mail server at the IP address. The important bit of info used by the mail client is the user login name - this tells the mail server what account, in what domain, to access.
-david

Hosting multiple web sites.

Dear members:
I am considering OS X Server for a personal project and would like some advice to help me decided what route to take.
My computer will soon be turned into a server hosting my web sites and some other services at my home office. I am thinking about OS X Server as I have done some research and found OS X to require quite a bit of work so that it can do virtual hosting.
How simple is it to configure virtual hosting in OS X Server ? I am considering the latest Leopard version in case it matters. I am not experienced and wish to employ an application that will simplify this process.
Any help will be very appreciated.
Thank you,
Joseph Chamberlain

Joseph:
Although I wouldn't touch any Web-server software other than Mac OS X Server, I should warn you that Apple occasionally favors "pretty" over "practical." I've used PCs and Macs since the Mac Plus was hot, and I've used OS X Server 10.3, 10.4, and now 10.5.3. The last is really excellent, with a gorgeous/powerful Server Admin user-interface, many supporting tools, and thousands of hardball features, but like many Apple "industrial-strength" software products, Mac OS X Server still contains a very few really BAD bugs -- or "oversights" if you prefer.
Before taking the plunge (maybe you already did?), read up on troubleshooting OSX Server's Postfix-based mail service. Even the 10.5.3 upgrade can turn "easy setup" into major frustration; you can do everything by the book and still have weird mail-server glitches. Don't even get me started on documentation for and "centralized" management of Open Directory, Kerberos, etc. I will be migrating to SSL mail security to avoid the user-directory thrash.
When trying to make OSX Server 10.5.3 (a clean install) host *multiple top-level Web domains under a single IP number*, Apple documentation online and on disc didn't offer enough setup detail and virtually NO troubleshooting. Google.com can find what's missing. This archived earlier forum thread saved my bacon....
Topic : "multiple web sites"
http://discussions.apple.com/thread.jspa?threadID=682507
In a nutshell: a multiple-website installation of OSX Server requires careful interaction between the domain-name, IP#, port#, and aliases for each site. When I created my several sites. I relied on the default installation (and Apple instructions) which leaves a wildcard "*" asterisk in each site's Web>Sites>Aliases>WebServerAliases field (in Server Admin). No matter how I diddled with each site's domain-name, IP#, and port# (to create unique combinations), I couldn't force the individual domains to get served independently (despite their shared static IP#) until I DELETED the wildcard WebServerAliases for all the sites. Poof, now it works fine.
Part of the problem is that Apple still publishes documentation on its legendary *drool-proof paper* ("do not expose your LaserWriter to open flame").

SCOT - Configuring multiple default domain

Hi,
Is it possible to configure multiple default domain in SCOT in a client?
I have set the default domain to e.g. "company1.com" and mails with this domain are sent out. However, mails with "company2.com" are not sent out. The message in SOST is "Delivery Attempted" and the mails were never received.
I tried setting the default domain in SCOT to "company1.com, company2.com" but it didn't work. So I'm assuming that it will only accept one default domain.
"company1.com" and "company2.com" are my subsidiary companies and not "yahoo" or "gmail" domains.
Thanks

Hi my friend
Default domain can be only one as it's called "default", which involves another setting: the SMTP mail host you define also can be only one, it can't work for 2 different mail domains.
Regards,
Effan

LDAP supporting multiple DNS domains

I have an environment with multiple DNS domains, and am configuring a Directory server (DS 6.3.1) to centralize various OS configuration maps including user authentication. None of the DNS domains have unique data, so I'd like to do something like storing all the real data in one suffix, then somehow have all clients look to that primary suffix. I am aware that the Solaris Native LDAP client wants to bind to a nisDomainObject that matches its DNS domain. I'm just having a hard time believing that I really need to manage all those individual suffixes when they don't have unique data requirements.
Take as an example the following domains to be supported: foo.example.com, bar.example.com, dev.example.com, qa.example.com, prd.example.com (no hosts are actually in "example.com", they are all in subdomains). Again, all share common configuration data, same user IDs, etc - no unique maps are required.
I created a suffix, "dc=example, dc=com", set it up with idsconfig. All is well there.
[A] My first thought is to bind all Solaris clients, regardless of their DNS domain, to the baseDN of "dc=example, dc=com" in order to avoid having a separate suffix for each DNS domain. I tried to do this using "-a defaultSearchPath=dc=example,dc=com" with ldapclient init, but it failed with an error indicating it wants to see the nisDomainObject of its real DNS domain.
The second though I had, which I don't believe is possible, is to find some sort of a LDAP equivalent of a symbolic link so that I could actually have an object for each DNS domain, but it would simply point back to "dc=example,dc=com". I can't find anything in the documentation which suggests this is possible, but I'd love to be wrong!
[C] Perhaps this could be somehow done with a rats nest of SSDs, but that really seems unwieldy, right? I plan on using a fair amount of the available objects, so it would be many SSDs per suffix. Yuck.
Can anyone comment on my above thoughts, or provide how they would go about supporting multiple DNS domains that have common configuration data?
Thank you,
Chris

Ok, I answered my own question. Turns out it's pretty easy. Just use the "-a domainName=example.com" option with `ldapclient` then make sure that the FQDN of the LDAP server is available (or use its IP address). My problem was that the ldapclient overwriting nsswotch.conf was clobbering the SSL session because I used the FQDN which couldn't resolve.
This leaves an interesting condition of having the output of "domainname" not match the DNS domain. I'm testing now to see if this causes any unexpected issues with our environmnet, but I suspect it's not a problem.

Lync 2013 certificate requirements for multiple SIP domains

Hi All,
I am engaged with a client in respect of a Lync 2013 implementation initially as a conferencing platform with a view to enabling EV functions (inc. PSTN conferencing) in the future. They initially need to support 30 SIP domains and eventually
around 100 SIP domains which is proving to be either not possible or severely cost prohibitive. Their current certificate provider, Thawte, can only support up to 25 SANs and have quoted them 5 figures. We tend to use GeoTrust as they are cheaper but they
appear to have a limit of 25 SANs. GoDaddy appear to support up to 100 SANs for a pretty reasonable cost. My questions are as follows:
Is there a way that I’m missing of reducing the number of SANs required on the Edge server?
Use aliases for access edge FQDNs - Supported by desktop client but not by other devices so not really workable
Don’t support XMPP federation therefore removing the need for domain name FQDNs for each SIP domain
Is there a way that I’m missing of reducing the number of SANs required on the Reverse Proxy server?
Friendly URL option 3 from this page:
http://technet.microsoft.com/en-us/library/gg398287.aspx
Client auto-configuration:
i.
Don’t support mobile client auto-configuration in which case no lyncdiscover.sipdomain1.com DNS records or SANs would be required.
ii.
Support mobile client auto-configuration over HTTP only in which case CNAME records are required for each SIP domain (lyncdiscover.sipdomain1.com, etc. pointing to lyncdiscover.designateddomain.com) but no SANs are required.
iii.
Support mobile client auto-configuration over HTTPS in which case DNS records are required for each SIP domain and a SAN entry for each SIP domains is also required. This is because a DNS CNAME to another domain is not supported over
HTTPS.
If the answer to 1 and/or 2 is no, are there certificate providers that support over 100 SANs?
How do certificate requirements differ when using the Lync 2013 hosting pack? I would think that this issue is something that a hosting provider would need to overcome.
Would the Lync 2013 Hosting Pack work for this customer? The customer uses SPLA licensing so I think is eligible to use the hosting pack but not 100% sure it will work in their environment given that client connections are supposed
to all come through the Edge where their tenants will be internal and also given the requirement for an ACP for PSTN conferencing.
Many thanks,

Many thanks for the response.
I was already planning to use option 3 from the below page for simple URLs to cut down on SAN requirement.
http://technet.microsoft.com/en-us/library/gg398287.aspx
What are the security concerns for publishing autodiscover over port 80? I.e. Is this only used for the initial download of the discovery record and then HTTPS is used for authentication? This seems to be the case from the following note on the below page:
http://technet.microsoft.com/en-gb/library/hh690030.aspx
Mobile device clients do not support multiple Secure Sockets Layer (SSL) certificates from different domains. Therefore, CNAME redirection to different domains is not supported over HTTPS. For example, a DNS CNAME record for lyncdiscover.contoso.com that redirects
to an address of director.contoso.net is not supported over HTTPS.
In such a topology, a mobile device client needs to use HTTP for the first request, so that the CNAME redirection is resolved over HTTP. Subsequent requests then use HTTPS. To support this scenario, you need to configure your reverse proxy with a web publishing
rule for port 80 (HTTP).
For details, see "To create a web publishing rule for port 80" in Configuring the Reverse Proxy for Mobility. CNAME redirection to the same domain is supported over HTTPS. In this case, the destination domain's certificate covers the originating
domain.”
I don’t think SRV records for additional SIP domain access edge is a workable solution as this is not supported by some devices.
As per the below article:
http://blog.schertz.name/2012/07/lync-edge-server-best-practices/
“The recommended approach for external client Automatic Sign-In when supporting multiple SIP domains is to include a unique Access Edge FQDN for each domain name in the SAN field. This is no longer a requirement (it was in OCS) as it is possible to
create a DNS Service Locator Record (SRV) for each additional SIP domain yet have them all point back to the same original FQDN for the Access Edge service (e.g. sip.mslync.net).
This approach will trigger a security alert in Windows Lync clients which can be accepted by the user, but some other clients and devices are unable to connect when the Automatic Sign-In process returns a pair of SRV and Host (A) records which do not share
the same domain namespace. Thus it is still best practice to define a unique FQDN for each additional SIP domain and include that hostname in the external Edge certificate’s SAN field”.
===================
1. Basically the requirement is to initially provide Lync conferencing services (minus PSTN conferencing) to internal, external, federated and anonymous participants with a view to providing PSTN conferencing and therefore enterprise voice services later.
2. The customer currently supports close to 100 SMTP domains and wants to align their SIP domains with these existing domains. The structure of their business is such that “XXX IT Services” provide the IT infrastructure for a collection of companies who
fall under the XXX umbrella but are very much run as individual entities.
Question:
Would you agree that I’m going to need a SAN for every SIP domain’s access edge FQDN?
Thanks.

Lab setup multiple SIP domains for federation

I have been setting up multiple Lync 2013 lab environments and have a question about my external DNS environment. I have installed server 2012R2 on the host running the lab with its own domain (contoso.local). I have this server which hosts a separate domain,
Hyper-V and a CA, this is what I am using for my external environment. The network IP is 10.0.0.0/16.
I set up a server called vRouter that has 3 NICs. In Hyper-v I have 3 virtual switches configured. One for the External environment - 10.0.0.0/16 (not necessary for lab, setup to transfer needed files from internet to VMs), one for 192.168.1.0/24, and one
with 192.168.2.0/24. The virtual router has RRAS installed and can route traffic between 192.168.1.0/24 and 192.168.2.0/24.
My VMs for the lab are as follows.
1test.local
AD1.1test.local -192.168.1.100
FE1.1test.local - 192.168.1.200
Edge1 - 192.168.1.210int, 10.0.5.10ext
2test.local
AD2.1test.local -192.168.1.100
FE2.1test.local - 192.168.1.200
Edge2.1test.local - 192.168.1.210int, 10.0.6.10ext
Both environments have users that can log into lync and message each other.
When installing the Edge servers I used the same FQDN and IP for the external interface since all ports are open and firewalls have been disabled internally. I installed the internal certificate from the AD server which has CA role in each environment. On
the external device I used the Host's CA to get certificates for both Edge servers. The Edge servers have 2 NICs one on their expected internal environment with no Gateway. And one on the external environment. These servers are not part of any domain. however
I did add the contoso.local to the primary DNS suffix when domain membership changes under system properties. I then created the two following A records on the host computer (10.0.0.0\16 network, contoso.local) to be able to see router their external traffic.
Edge1.contoso.local 10.0.5.10
Edge2.contoso.local 10.0.6.10
Both of these FQDNs are what is in my topology for the Access Edge service, Web Conferencing Edge Service, and A/v Edge Service with the same IP using different ports in both environments.
Both environments are set up to support the other SIP domain. However when I try to add a user from the other domain I cannot communicate with that user nor see their presence.
I looked over my external DNS settings and realized that I had not set a SRV record on the 10.0.0.0\16 network(external).
I then realized that if I try to add the traditional _sipfederationtls._tcp.contoso.local I will have 2 conflicting entries.
One for:
_sipfederationtls._tcp.contoso.local - 10.0.5.10 (1test.local edge)
and one for:
_sipfederationtls._tcp.contoso.local - 10.0.6.10 (2test.local edge)
Should I spin up another VM and make that a DC with a CA and trust it to the host computer, set up conditional forwarders. Something like Trust.local and correct the DNS, topology builder FQDN, and certificates on the second edge server?
Edge2.trust.local
Or can I add a new zone to my host computer then correct the DNS, topology builder FQDN, Certificates?
Or am I missing another external DNS record on my contoso.local environment?
Can I set up a CNAME entry that will mask the second edge server?
Any input would be appreciated.
Thanks

If contoso.com is not a sip domain, then you won't need that DNS record at all. Those records are autodiscover records that Lync uses based upon the sip domain.
So you'd need
_sipfederationtls._tcp.1test.local
and
_sipfederationtls._tcp.2test.local
What effectively happens, is when someone on the outside tries to IM
[email protected], their Lync edge server will see the 1test.local and query the appropriate above record for it so it knows where to communicate.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

How to delete multiple data domains with single step ?

how to delete multiple data domains with single step ?

You can go to your Endeca-Server domain home e.g.($WEBLOGIC-HOME$/user_projects/domains/endeca_server_domain/EndecaServer/bin)
run
[HOST]$ ./endeca-cmd.sh list-dd
default is enabled.
GettingStarted is enabled.
endeca is enabled.
BikeStoreTest is enabled.
create a new file from the output just with the domains that you want to delete and then create a loop
[HOST]$ vi delete-dd.list
default
GettingStarted
endeca
BikeStoreTest
[HOST]$ for i in $(cat delete-dd.list); do; ./endeca-cmd.sh delete-dd $i; done
Remember that this can not be undone, unless you have a backup.

Noob needs help with hosting multiple sites

Hello I am new to this multi hosting. I have looked on the forum for answers but haven't found any. I am trying to figure out how to host multiple sites. I have my dns working for my default site "example1.com", but need to know if I need to add another dns record for my second site. "example2.com". Also when I point to the new fold that has the second site in it and I assign it port 82 for testing purposes I get an error message saying 403 access forbidden. I need to find out how get permission to view the site for the public. Its in a separate folder on an external hard drive right now for testing purposes. Can any body help me or point me in the right direction? Thanks so much!!!
-Kcam1999

{quote}
While what you are telling him is technically functional, it is not correct
I beg to differ, Paul. You are the one that is not correct.
CNAMES have been deprecated as of some years ago
What? huh? really?
Please show me any official document that states this (and not someone who just started a rumor because he didn't understand them). Indeed, the DNS RFC makes no such claim.
{quote}
I stand very much corrected. CNAMEs are not officially deprecated. Interestingly, your post cites precisely what happens when CNAMES used carelessly. How many transactions are needed to resolve Apple's CNAME chain below? RFC1912 (http://www.faqs.org/rfcs/rfc1912.html) has some recommendations that suggests Apple's own network folks have, like me and perhaps even others here, some learning to do. Is that a 'best practice?'
{quote}> Then make sure you tell Apple since this site depends on the use of CNAMEs:
dig discussions.apple.com
discussions.apple.com. 492 IN CNAME discussions.apple.com.edgesuite.net.
discussions.apple.com.edgesuite.net. 4427 IN CNAME a1399.b.akamai.net.
a1399.b.akamai.net. 2 IN A 128.241.220.82
a1399.b.akamai.net. 2 IN A 128.241.220.72
In fact, it uses TWO CNAMES in a chain. Oh my.{quote}
From RFC1912 (which I'm sure many have now read here), section 2.4 is as follows:
{quote}... having chained records such as CNAMEs pointing to CNAMEs may
make administration issues easier, but is known to tickle bugs in
some resolvers that fail to check loops correctly. As a result some
hosts may not be able to resolve such names.{quote}
{quote}> It is not valid to say "don't use these because they could cause problems'. A records can be just as problematic, as can PTRs. Let's not even talk about MX.{quote}
How, exactly, does is an A record problematic? No chains, no additional lookups, no wasted cycles...
We differ here -- and if we are dealing with a newbie, we don't need to enter into unnecessary complexity UNTIL it is a requirement for their solutions.
{quote}> There are many valid reasons to use CNAMEs in DNS, not least of which is the ease of moving a service if it uses CNAMEs. For example, if you have 10 A records all pointing at the same server and you want to migrate to a different machine you have to locate and update all 10 records. If they used a CNAME to the physical server you could move them all at once using a single change. This is especially important in cross-domain links where you may not control all the origin zone files.
{quote}
You're somewhat reaching here, and it is well beyond the scope of the OP's post or needs (well, until they tell us more about their needs, I suppose). There is nothing difficult about 'finding' and updating the necessary records. The final example you gave is a good one and I'll say THAT is an appropriate use of a CNAME, 'though there are other workarounds for it.
Thanks for keeping me honest.

Hosting Multiple Mail Domains

Similar Messages

Maybe you are looking for