I have a website hosted on a cPanel, I need to change it to Cloudflare nameservers and then the dns records so the main domain will be pointed to a vps ip address and the mx records keep using cPanel records. The problem is I found a lot of TXT records created by the cPanel and I don't know what I should take or leave since they look so random.
My cPanel DNS Zone Editor:
Notice:
I have two active domains on my cPanel, the first is the main domain which I would like to transfer to point to my vps, the second should keep working on the cPanel. but I found related txt records in the first domain, looks like this caldav._tcp.DOMAIN2.tn.DOMAIN1.tn. (check screenshot)? Why does it even exists in the main domain records?
I just need to move the main domain and keep the mailing service with cPanel! Which TXT records should I create on Cloudflare after I change the domain nameservers?
If you are planning on keeping your eMail where it is but only plan on changing the web site to use CloudFlare you should really leave ALL of these TXT records as they are.
SPF = Sender Policy Framework (which is a list of servers or services that can send eMail using your domain name)
DKIM = Domain Key Identified Mail (is a form of anti-alteration system to stop eMails being altered in transit)
DKIM is unique to each domain and subdomain so if you have a eMail service on the second domain you should have an SPF & DKIM record for them too.
As for the bottom rules I don't know what they are.
Related
Quick Question.
A guest house was bought by the original owner and scenario as follows.
The Website for that guesthouse is on its own Hosted WordPress installation at the current host
The login address would be https://Example/wp-admin
I re-created that user account on our hosted WHM as I need to transfer the website and Domain to myself.
Can I login to the newly created WP-admin on my server while the A record is Pointed to the current hosts IP?
Example
Current Host
Example/WP-admin
IP:46.0.0.0
Example
New Host
Example/WP-admin
IP:76.0.0.0
How Can I login to the WP on the new host if the DNS is pointing to the IP:46.0.0.0 (Current Host)
FYI - most will ask why don't I point the A record, that's because the current host does not have the logins for the Cpanel, nor are they answering calls
THANKS,
hope this makes sense in the way I phrased it.
On your local machine you can change the hosts file to point Example webstie to 76.0.0.0 and then you can flush the dns cache and web browser cache. From now on Example website will point to 76.0.0.0 for your computer only. If you have a Windows machine and admin access, you can modify the hosts file under c:\Windows\System32\Drivers\etc\hosts ( change c partition to the partition that you have installed your windows on, if its different then "c" ) then you can add following line:
76.0.0.0 example.com www.example.com
Please make sure you flush the dns cache and clear the web browser cache afterwards.
If you want the whole world to see Example website from 76.0.0.0 you would have to change the A record.
I know this question has been asked numerous times here but I still don't get the solution, sorry about that.
I deployed a wordpress multi site VM on my Azure account and purchased a domain name "https://jobinwrites.com" from Azure DNS service. I followed the instructions here to map an "A record" to the IP address of this Azure VM:
And this is how the overview of the Azure VM looks like:
When I hit the IP address of the machine or the jobinwrites.westus.cloudapp.azure.com domain, I correctly hit the service. However, when I try jobinwrites.com, the browser returns a DNS address not found exception. What am I doing wrong here? Thanks in advance.
According to your description, you want to map a custom domain name to your Azure VM, we should buy this custom domain name first.
Azure DNS is not the domain registrar.
We should login your 3rd party domain register configure page.
Each registrar has their own DNS management tools to change the name server records for a domain. In the registrar's DNS management page, add a new A record, like this:
Host type value
xxxxx A 104.42.230.37
If you want to add a CNAME record, please refer to this answer.
I manage a hosting server using WHM. I have two cPanel accounts on this server, one for exampletest.com (account name is exampletest) and one for example.com (account name example). We have a Wordpress site that was working well at exampletest.com but we keep running into problems when we try to migrate it to example.com. I believe it has to do with one WordPress plugin that doesn't migrate well.
So we had the idea to simply take the example.com domain and point it to the exampletest cPanel account, then update the domain for WordPress in the database. However, one potential issue I can see is that we have many active email addresses on the example account. I fear that associating the example.com domain to the exampletest account will break the email addresses.
Keeping the above in mind, I have a couple questions:
Will associating the example.com domain to the exampletest account break the emails? If so, is there a workaround (moving the email addresses to the new account somehow?)
Is there a better way to go about doing this that I'm not thinking of?
The best way of transferring your wordpress site would be to copy the files, create a database user with the same login details and import the database. Wordpress shouldn't be able to tell the difference.
One way would be to assign a static IP address to exampletest and point example.com's A record to that IP.
Due to the way WHM's DNS and port binding is set up it will not let you set up the same domain on two seperate accounts.
You could treat www. as a seperate subdomain and add the subdomain www.example.com to exampletest as an addon domain and remove the www A record from example first. Redirect all web traffic from example.com to www.example.com or use another sub-domain such as www2.
Another option would be transfer the emails, you can either use the transfer tools in WHM > Transfers or use http://imapsync.lamiral.info/
I have a wordpress blog hosted on blog.company.com, and now I'm trying to create a DNS entry on Heroku to get mycompany.com but I get the following error:
! could not create zone; already registered on Zerigo to a different account?
What am I missing herE?
Thanks
At a guess there's already an account on Zerigo that has the zone mycompany.com registered to it.
You can't (easily) have a domain hosted on two seperate DNS providers, you're best option would be to find the DNS host of blog.mycompany.com and setup a subdomain on the mycompany.com domain, eg www as a cname entry to proxy.heroku.com and then add www.mycompany.com as a custom domain on your heroku application.
The fact that you're getting the message about a duplicate zone, is Zerigo already hosting the DNS for blog.company.com perhaps? In which case login to the control panel for that (the zone is company.com) and add a record for your site.
I am working on an ASP.NET MVC web app that allows people to publish content, but other than publish the content to a remote server, I want to allow people to use their domain name directly. For example, the user "Tom" can have his domain name TomSite.com point to http://www.mywebapp.com/user/tom, but the sub path will also be mapped. For example, TomSite.com/path will be mapped to www.mywebapp.com/user/tom/path, and this is transparent to the web visitor. The visitor will never see "mywebapp.com" anywhere on TomSite.com.
I think Smugmug.com provides such service, to allow people to use their own domain name for the photo portfolio. I want to achieve the same result.
How can I do this? Thanks!
This require multiple steps.
First you have to find out how your users will configure their domain to have a CNAME record for you site. You can archieve this in a number of ways where the best is education. Making partnerships with hosting providers requires a great deal of volume.
In IIS this will require you to either add each host name manually (however this could also be archieved through scripting) or have a dedicated IP address only for you site.
There is also a need for the domain to be associated with an account. The user has to add this themselves and you would probably add a check in the interface which confirms the domain is pointed at your server. The code for this would look like (remember to include the System.Net namespace).
if (Dns.GetHostEntry("www.user.example.com").HostName == "www.example.com")
{
// www.user.example.com is a CNAME for www.example.com
}
In you ASP.NET MVC project you need to implement routes for this particular purpose. Create a custom class inheriting from Route which also takes the domain into account.
Smugmug (who you mentioned) get their users to setup a CNAME record that will alias the url for the user's personal photo section. For most users this will probably require them contacting their host or looking up help files in order to get it all setup.
So, while www.tomsite.com could transparently serve up pages hosted at www.mywebapp.com the users will have to put some kind of effort in. To make it a completely seamless you will need some kind of arrangement with the users web host (Smugmug appear to have such an arrangement with GoDaddy).
I doubt you will be able to setup such integration with all the web hosts out there, so the only complete solution would be to host the websites of your users yourself (I do not know enough about your wider situation to determine if that is a reasonable solution).
Note: setting up an alias on your own web server (aka url rewriting) will not work, unless you host their site yourself, as obviously people fetching from your user's domain will not arrive at your server in the first place.
Have each customer's friendlyname pointed at the external ip address of your webserver.
Use IIS to resolve the friendlyname specified in the host header request to the logical website you want delivered to that friendlyname. IIS will happily map both a website and a virtual folder to the same folder in the file system. Create a website for each customer. Then bind that website to the customer's friendlyname.
Remember to map the default website only to your own friendlyname(s). If you leave it in promiscuous mode (mapped to "*") results will be unpredictable.
To set host header mapping
Select Default Web Site under the Sites node. In the Actions pane at top right click on Bindings... to open the Site Bindings dialog. There will be a list of bindings, probably containing a single entry that says http * 80. Select this and click the Edit... button. Set Host name to your own friendlyname.
Run IIS7 Manager and for each customer site create a website under the Sites node. Set both file path and host header binding while you are creating each web site. Obviously the host header binding (host name) should be that customer's friendlyname.
Just make a new record in your webserver setting tomsite.com directly to your mywebapp.com/user/tom/ path ?
See it like an alias :)
Ofcourse, since you're asp.net/windows based, i think you'll have to digg deep into IIS to automate this kind of stuff. If you were on apache it would be adding 3 simple lines to httpd.conf.