i am plaining to install exchange 2013 , my internal domain name is abc.local
And external Domain name is xyz.com
now want to create my email id on xyz.com (external) this is ideal situation .
I am adding my external domain to alternative UPN suffix in ad
And creating a zone in my dns with external (xyz.com) now my dns have 2 zone..(abc.local and xyz.com) Now I am
confused about my records (autodiscover, mail,mx)
Where exactly I will create these records ? in internal zone or external ?
Please suggest
If I am doing anything wrong pls let me know
You'll be taking email from xyz.com so you'll only want an MX record for xyz.com in your "external" zone (public DNS record). Point that record to whatever IP your SMTP receiver/mail gateway lives on. Validate with mxtoolbox.com.
An example: I have an MX record of abc.com. It's IP is a public IP on my firewall. That NATs to a DMZ IP which lives on an Ironport mail gateway. The Ironport mail gateway then delivers the mail to Exchange CAS SMTP receiver configured to only listen to the Iornport internal IPs. Works great.
From there, you configure xyz.com as an authorative domain in Mail Flow (via Exchange Admin Center) via: Configure an accepted domain within your Exchange org...
Your recipient policy should auto create emails based off this domain when you build a mailbox and from there you'll be able to test. After that, worry about outbound, a whole different process.
-Chase
Related
So, setting up a brand new domain for the very first time (never set up a brand brand new domain) of Azure boxes (but not AAD - using traditional AD over Azure) trying to get these boxes to communicate has taken me literal days and I am getting very frustrated at these.
DC is VT-EDD-Server
Domain is VT-EDD.local
Client is VT-EDD-IIS1 (I'll have others, but once this is fixed I'll have this solved)
Not sure if I even NEEDED to, but I added the IP for the DC and domain to the client's host file, and now I can ping the server. I have also updated the client's DNS to:
and when I still try to join the domain I get
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "VTT-EDD.local":
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.VTT-EDD.local
Common causes of this error include the following:
- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
168.63.129.16
- One or more of the following zones do not include delegation to its child zone:
VTT-EDD.local
local
. (the root zone)
I can ping both the DC and the domain by name and IP, but can't join it.
After creating a ADDC in azure, joining the server to it, and adding the DC's IP to the DNS in Azure, I was able to complete the process.
I want to upload my local wordpress to the domain I bought and make it live. But I don't know how to add domain and add dns in oracle cloud.
Unfortunately, there's no simple answer to your question. The general documentation on using Oracle Cloud DNS Service can be found here. Below is a quick summary of tasks that need to be completed:
Note the public IP address assigned to your compute instance that's hosting the web server. Assign one if necessary. The compute instance must be on a public subnet to be assigned one.
In your tenant's root compartment, create a Zone for your domain, e.g. example.com.
Create an "A" zone record, e.g. www.example.com => 123.123.123.123
Publish the record.
On your Registrar's DNS management console, update the name server records to point to Oracle Cloud's name servers assigned to the zone.
I tried creating an Amazon EC2 instance with an elastic IP address. In there I deployed a MEAN app by Bitnami.
On the other hand we have a CPanel (not deployed in amazon, I think it's Apache, not sure, I'm not the one who deployed it)
Cpanel is already pointing to www.example.com so we can access cpanel via www.example.com:2082 but the default www.example.com:80 is blank/empty. We are using Cpanel for our mailing server.
What I need to do is to point Amazon EC2 public IP and DNS to www.example.com:80. Can I set it up in Cpanel DNS Zone Editor? or do I need to set up Amazon Route 53? what do I need?
If I create a new A record in Cpanel DNS Zone editor for Amazon I lose access to Cpanel www.example.com:2082. I'm really confuse right now. Please Help.
You need to introduce a Proxy server in between to do this, As in DNS you can't set the ports, for each type of requests ports are already defined.
You can add nginx or haproxy or any other reverse proxy server, which will accept all the requests and passes on the request to appropriate hosts on appropriate ports.
I know it's a bit late but just in case you still need it or someone comes across this:
No need for a proxy.
You point the A record for example.com to EC2 IP.
CNAME for WWW to example.com
Then you should have an A record for mail.example.com for your cPanel IP
Your MX records should point to mail.example.com and not to example.com.
And you can access cPanel at mail.example.com:2082 or whatever the server's IP or main hostname is. The main hostname has the advantage that you can use port 2083 for SSL cPanel connections
Just make sure the e-mail clients use mail.example.com and not example.com as the connecting mail server.
I am working on a project, where I have a domain xyz.com, I have been requested that a subdomain example abc.xyz.com should point to website which has ipaddress
example http://199.152.57.120/client/ and when a visitor browse abc.xyz.com it should open the website hosted on http://199.152.57.120/client/ but by hidding this ip address the visitor should always see abc.xyz.com.
I also need to host another website to xyz.com
domain which is registered with x company and webhosting is taken for z company both different.
It is something similar to Reseller business where Reseller company assign a website to their client on their custom domain.
You can make A record in your DNS Server that IP address 199.152.57.120 pointing to abc.xyz.com
and then make same configuration in your web hosting that nginx/httpd virtual host point to directory /Some/Directory/client
you can read this for nginx https://www.linode.com/docs/websites/nginx/how-to-configure-nginx
It can be easily done in domain provider DNS zone. Just add A record where you will provide subdomain ex: abc.xyz.com and connect to adress ex: 1.2.3.4 How to do that in your domain provider, just check help pages for DNS records.
Alternatively you can install proxy software like NGINX and make subdomain redirect.
Example setting:
From where do I get the correct syntax to create a proper SPF record for EC2 amazon server? I understand how to create a dns entry but I have no idea what to put in place for the SPF record.
This is very easy to do:
Provision an Elastic IP for your server
Setup an "A" record for the server which will be sending mail with your favorite registrar- a good practice to follow is to include "svr" somewhere in the hostname, as in, app-svr-01.youdomain.com
Click here to contact amazon and ask for a reverse dns record for the IP
add the following somewhere in your SPF record and you should be good to go:
a:app-svr-01.youdomain.com
Note: if you need to relay mail through this server from your other AWS servers, or communicate between servers in any other way, you shoukd not use this new FQDN, but rather the AWS FQDN from the AWS console (it will look like ec2-xxx-xxx-xx-xx.compute-1.amazonaws.com).
Using your custom domain name will route through the "WAN" and incur bandwidth charges.
You can use the Amazon Simple Email Service (SES). If you only use this service (and not directly), then your SPF can be as simple as described in the FAQ:
http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/SPF.html
maybe changing it to a definite fail on mismatch:
v=spf1 include:amazonses.com -all
Creating an SPF record for an EC2 instance is a waste of time. Every major ISP and blacklist will blackhole mail from an EC2 IP no matter what you do. Since anyone can spin up an instance, get a new IP, send spam and disappear, nobody trusts their mail.
Use an external mail server, like SendGrid.