Openshift domain (example.com) requires a CNAME pointing to my example.rhcloud.com. However by doing this, and not allowing us to do an A record with IP they are breaking the ability to do an MX record for example.com since an MX record requires that example.com be an A name not a CNAME.
Is there a way around this? I'm using namecheap.
I've seen some hacky stuff to point to www.example.com but I don't want to do that, as I want to remove the www. from the domain.
Its not possible with openshift, because example.com needs to point to an A record for mx.example.com to work properly. Its required by the RFC spec.
Because openshift requires you point example.com to a CNAME (foo-whatever.rhcloud.com), you cannot then point mx.example.com to an IP of email server and expect mail for me#example.com to work.
There are some hacky solutions, like using 3rd party dns resolver and cronjob to update the IP address of the openshift server, but none of these seem like solid solutions to me.
https://www.openshift.com/forums/openshift/methoddynamic-ip-for-your-apps-a-record
OpenShift Online is not a dns provider, you can not create an mx record using it. You would need to create an MX records at your dns provider for your domain.
If you mean "how can i create an mx record using my dns provider along with having a cname for openshift", then you would need to create an mx record that points to your third party mail service.
You can check out this answer (https://serverfault.com/questions/100064/dns-is-it-valid-to-have-an-mx-record-and-no-a-record) which should help you.
Some DNS providers support special types of DNS records that dynamically look up dynamic IP adresses and create the corresponding A records.
DNSimple calls this an ALIAS record.
DNS Made Easy calls it an ANAME record.
You can use these special record types instead of CNAME, if your DNS provider supports them.
Related
It's may be stupid, but I really interested in this question.
I want make mirror www subdomain for main and can't choose which property to use...
CNAME looks more solid and clearer. I can set it like this:
www.exmaple.com -> A someIP.
Just don't quite know how Google Cloud DNS behaves. If use CNAME, will the client get an subdomain IP or will he get the name of the main domain and make a second request to get his IP?
P.S. Yes, I understand that the time difference in the execution of requests is so small that should forget it.
Google Cloud DNS does not support ALIAS resource records.
ALIAS (A) records are usually faster and are typically used for internal services on the same provider. Example would be a load balancer. ALIAS records typically have a short TTL (typically 60 seconds) so that they are constantly being resolved to the service.
When you resolve a CNAME, a subsequent lookup is required for the returned DNS name, which could then be another CNAME, etc.
There are more factors to consider when select an ALIAS versus CNAME. For example:
AWS does not charge for ALIAS record lookups but does for CNAME lookups.
You cannot use a CNAME for the zone apex (example.com). You can for the subdomains (www.example.com).
A CNAME cannot coexist with another resource record of the same name, whereas ALIAS can.
most domain providers don’t allow setting a CNAME record for a main domain. It’s usually only possible to set CNAME records for subdomains.
So now I’m wondering if it would be possible to set an A record instead, pointing to scapp.io’s IP address. I tried it yesterday and it seems to work great but I’m worried that IP address might not be stable.
Any ideas whether setting an A record to 194.209.246.110 is a valid option for configuring a "naked" domain?
We don't recommend A record to IP address. The IP addresses may change without prior announcement.
See docs.developer.swisscom.com -> DNS for Domains for other options than CNAME.
Configuring DNS for Your Registered Root Domain
To use your root domain (for example, example.com) for apps on App
Cloud you can either use custom DNS record types like ALIAS and ANAME,
if your DNS provider offers them, or subdomain redirection.
Note: Root domains are also called zone apex domains.
If your DNS provider supports using an ALIAS or ANAME record,
configure your root domain with your DNS provider to point at a shared
domain in App Cloud.
What domain provider do you use?
I have a question about setting up my mailserver settings. I have a website on azure, so in my DNS settings at my reseller, i set up tot point domain.com to domain.azurewebsites.net.
Website is working fine, so far so good. Now i want to use a mailserver, hosted somewhere else, because azure doesn't provide this out of the box.
In my DNS settings i set up the MX record to point to my other hosting where i have a mailserver defined.
domain.com MX mail.domain.com
mail.domain.com A "ipadress mailserver"
When i try to send a mail using my mailcredentials and mail.domain.com as smtp server, all works fine. But i can't receive email messages. Is it possible to set this up if my main domain will point to azure?
Seems like i found a solution. You should not use a CNAME for the root domain as this is also used to resolve the MX record. So just add an A record for domain.com instead of a CNAME and the MX record will be reslved properly. Off course, azure does not recommend an A record because the IP address can change, but this is only when you change plan or disable/enable your website.
I have about 300 domains using my company DNS ns1.x.com.br and ns1.x.com.br
I want to use CloudFlare with all those 300 domains but when I add a domain to CloudFlare they give me new DNS that I need to change in my domains.
So far I added 70 domains to CloudFlare and they gave me only 3 sets of primary and slave DNS.
So, can I point my ns1.x.com.br to the primary DNS provided by CloudFlare? And do the same with the slave?
After that I will create a ns3.x.com.br and point it to another CloudFlare DNS. Will it work?
CloudFlare works at the DNS level in this way:
You have to signup for CloudFlare and add the domain (make sure all of your DNS records are in your DNS zone file at CloudFlare).
You then change to our nameservers at the registrar.
Only our nameservers can be at the registrar.
"So, can I point my ns1.x.com.br to the primary DNS provided by CloudFlare? And do the same with the slave?
After that I will create a ns3.x.com.br and point it to another CloudFlare DNS. Will it work?"
These records should be in your CloudFlare DNS zone file for the site(s) on those nameservers. They can't be active at the registrar because only CloudFlare's nameservers can be there for our service to properly work.
Note: I'm not sure if you're providing commercial hosting for sites. If yes, you might want to look at becoming a CloudFlare Hosting Partner instead (you don't have to worry about changing nameservers).
Yes, you can. There is a possibility to add domain in the new name server first you need to know the domain secret of each domain(It's a 6 Digit pin maintained with your current DNS)Theft Protection pin also needed. Both are same in the ResellerClub.
If you are using ResellerClub means Its Really easy to change, Because it has a Bulk Domain Booking option. That have a option "add existing Domain" option.
If You have any other Problem. Or this not a exact answer you need, Then please chat with me. I will update the answer. Thank You...
Could someone explain the difference between an A Record and a CNAME, and what I should be telling my users to do if I am building a site that allows for custom domains to point to a subdomain on my hosted service?
A record... www.rabbot.com -> 123.123.123.123 (ie. an actual IP address)
CNAME record... www.philip.com -> www.rabbot.com (ie. more like an alias)
Your life will be much simpler if you have your users to use a CNAME as they can point their domains to yours. Then if you need to update your server's IP address you can simply update the single A record you have instead of making all your users update their DNS entries.
This is true regardless of what web framework you are using...