Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I have a problem.
I own a small hosting company. I am trying to add Cloudflare to my site as a free CDN. The only problem is when I sign up I have to change the nameservers to their nameservers. I already have nameserver DNS set up through GoDaddy, so how do I add them to CloudFlare? My main site uses my company's nameservers already but whenever I add them the site goes offline.
When I go into Cloudflare's DNS records I click on the dropdown, click NS, and there's two boxes that say 'Name' and 'Nameserver'. Does this mean I input 'NS1' into 'Name' and 'NS1.DOMAIN.COM' into 'Nameserver'? Where do I input my server's IP addresses?
Is there another way of accomplishing this with the free version of Cloudflare?
That is just impossible. Option to have custom name servers available only on Business and Enterprise. See https://www.cloudflare.com/plans.
Also, you might mistaken. You must change name servers in your domain register settings, not on CloudFlare.
An old question (no doubt you found the answer long ago), but nevertheless still an interesting one! I recently faced this issue and would like to share what I did.
If I understand the question correctly, you are using child nameservers at your registrar to point your customers' domains to your server?
In cloudflare, after you have added your primary domain, you can also specify the NS record to allow customer domains to continue to use your custom / child nameservers at your registrar.
In the DNS records control panel, simply choose NS from the dropdown field, then in the Name field, add your child nameserver, then in Ip4address field, add the nameserver so it looks like e.g.
NS yourdomain.com managed by ns1.yourchildnameserver.com
Do the same for NS2 and your customer domains should continue to resolve without any issues.
In the end of course, it would be better to add each customer domain into CF ad point their DNS directly to your server, but the above steps should work as an interim measure.
Hope this helps someone else.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I setup my website for one of my subdomains e.g. app.mydomain.com
From my website, I'm trying to send emails using info#mydomain.com.
I don't have much experience in setting DNS records. I'm trying for weeks but my emails are going inside the spam. I talked to mydomain.com hosting providers and they set DKIM records and suggested to add SPF records as well:
mydomain txt "v=spf1 +a +mx +ip4:XXX.XXX.XXX.XXX +ip4:XXX.XXX.XXX.XXXX include:relay.mailchannels.net ~all"
Even after adding this record, my emails are going inside the spam folder with softfail. I don't know what I'm missing.
One thing, my app.mydomain.com and mydomain.com are hosted on separate servers that's why I've included ip4 for both websites.
I've read that we need to add different SPF records for different domains/subdomains but not sure if I need to add a separate SPF for my subdomain when I'm using mydomain's email address for sending emails. I feel like I'm stuck in a loop.
Can someone please assist me or guide me what should I look into to get to the right track?
Looking at the SPF record you included, it seems to be the incorrect format to include "subdomain" after the ip4. This should be only an ip address, not a domain.
You may want to do some testing / validation with the tools found on this site - https://mxtoolbox.com/SuperTool.aspx
ipv4 expects an IP(ipv4). So you should change your SPF to something like this:
"v=spf1 a mx ip4:XXX.XXX.XXX.XXX ip4:XXX.XXX.XXX.XXXX include:relay.mailchannels.net ~all"
To test, use https://mxtoolbox.com/SuperTool.aspx?action=YOURDOMAIN&run=toolpage.
A good DKIM configuration will help you too.
;)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am reading a book on DNS to expand my knowledge. I am not able to grasp the difference between subdomain and zone. I understand that domain is the big umbrella that has multiple zones (ca domain). Then subdomain is test.ca
But then what is zone? Isn't test.ca also a zone that nameserver loads?
Domain name servers store information about part of the domain name space called a zone. The name server is authoritative for a particular zone. A single name server can be authoritative for many zones.
Understanding the difference between a zone and a domain is sometimes confusing. A zone is simply a portion of a domain. For example, the Domain Microsoft.com may contain all of the data for Microsoft.com, Marketing.microsoft.com and Development.microsoft.com. However, the zone Microsoft.com contains only information for Microsoft.com and references to the authoritative name servers for the subdomains.
The zone Microsoft.com can contain the data for subdomains of Microsoft.com if they have not been delegated to another server. For example, Marketing.microsoft.com may manage its own delegated zone. Development.microsoft.com may be managed by the parent, Microsoft.com.
If there are no subdomains, then the zone and domain are essentially the same. In this case the zone contains all data for the domain
Subdomain is a relative term for lower level domains. A subdomain may equal one or more zones.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I have a domain which I want to redirect to a AWS cloud front URL.
If I only add a redirect at my domain provider then browser shows the cloud front URL in address bar which looks ugly.
I can create a CNAME record with the cloud front URL to a sub-domain, but not directly to the domain, but I do not want user to type the complete sub-domain name.
I tried adding a combination of (1)a redirect from domain to the sub-domain and (2) a CNAME record from that sub-domain to the cloud-front URL. But, of course, I get "too many redirects".
What is the correct solution for this? Will any Route53 service fix this problem?
I changed the name server on my DNS to AWS route-53 ones and then added a record to the Alias pointing to my cloud-front distribution. In Cloud-front, I had to set my domain name as the Cname.
An alternate solution, and effectively another way to create virtual record, could have been as discussed here in "The Solution" section. Unfortunately my domain registrar(1&1) doesn't support this feature.
[Edit 06/27] I tried CloudFlare's CNAME flattening feature and that works as well.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
Not sure how to word the title.
I am in this situation...
I have had a website for a long time now where the domain name and hosting are managed by OVH. A few years ago, I setup the email service through Protonmail with a custom domain. To do this, I changed some things in the DNS Zone so that emails will be routed through Protonmail. I would have to go back and look at exactly what needed changed...
Now however, I am becoming unhappy with the hosting provided by OVH, so I would like to try out another host. The issue is that to switch hosts, I could either
Transfer the domain to another provider, and then setup the email from scratch.
Switch the nameservers at OVH to point to hosting somewhere else (e.g. A2Hosting).
I would prefer to take the second option, since this would allow me to try out a different host without having to reconfigure my email. If I like the host, then I would probably move everything over to them. But I simply don't know if it is feasible. So is this possible? And if so, how would I do it?
I am worried that if I just switch the nameservers at the host, then my email would be offline.
You are right, if you change the name servers you will not be able to receive mails (unless you configure the MX records at the new provider). In you case you can simply create 2 A records pointing the root domain (example.com) and * (which is for all subdomains, that don't have their own records, so www.example.com and something.example.com will work, as long as there are no other records for them).
For more information about the records configuration you better ask your new host.
And when you are happy with the new hosting you can change the name servers or transfer the domain or do whatever you want. Note that the web host, the domain registrar and the DNS host may be from different providers, it's not a must to have all the services at one place.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I have a website hosted in Switzerland and the domain registrar is in the US.
If I requested a transfer of the domain from the US to the registrar in Switzerland, what technical advantage would that give me, if any?
Are there any significant things to pay attention to apart from little things (such as price)?
If not I would leave it in the US then and just change dns records...
Thanks for any feedback!
The link between domain name and hosting (IP address) is simple an ip address corresponds to a name. But for a name to be valid and some people to have jobs there are additional steps:
Root name servers -> Authority name servers slave nemeservers
The registrars provide a list of authoritative name servers coupled with names to the root servers (this is called glue). Usually the person owning a domain can change the authoritative name servers via some panel.
That being said the only technical advantages i can think of are:
Price for the registration (per year)
Willingness of the registrar to shutdown a domain under pressure on or request
the registrar can change the Name servers and point the domain wherever he wants and can block you from changing this which effectively shuts down the domain.
Please also remember that in the end the registrars (the real ones also called NIC's) are not so much and usually can be found by simply typing .ext e.g. nic.com, nic.org
The other companies selling domains are just resellers and using any of them should be guided mostly by features they offer and price (e.g. how usable is their panel, how fast they respond to tickets, etc.)