Tag Info

New answers tagged

0

This is a requirement for all .uk second level domains (SLD). From Nominet Rules: Where a registrant address is not within the United Kingdom, a UK address for service must also be supplied. That's your "administrative contact". I don't believe this was a requirement for third level domains (eg. .co.uk).


0

You can choose not transfer your DNS to your webhost. To keep your current email configuration, you only need to point example.com to your ecowebhosting web server's IP address and set up www.example.com as a CNAME to example.com Hope this helps.


0

Use Round-robin DNS or a load balancer.


0

You have a problem that may not have occurred to you yet. To answer your question directly: Yes. You described it correctly. Now for the problem: You do not want to do this. You should never host your domain name on a network that requires your domain name. What happens if there is a problem?? I used to be a web host in my previous life. Yes. I did have ...


0

you are right. 1.buy a normal ssl certificate for 'yourdomain.com' 2.First create a mx record without mail. suffix yourdomain.com. 800 IN MX 10 yourdomain.com. Mx domain should be equal to ssl certificate domain that you use for mail server, Exim for instance. 3.The same ssl certificate to yourdomain.com can be used for a web server & mail ...


0

Instead of selecting forward with mask you need to select forwarding only. Putting it inside a frame is how they mask the domain the site is on.


0

It is perfectly acceptable to update /etc/hosts in cPanel/WHM. As a rule of thumb, incase of an update which may change the file (unlikely, cPanel doesn't tend to touch it after the initial install phase) run this command to take a backup. # cp /etc/hosts /etc/hosts.bak This will copy your hosts file to a new file in your etc directory called hosts.bak ...


0

You can do 1 of 2 things. You can either create a CNAME record for www pointing to xyz.tk. A CNAME record is essentially an alias record. The upside of this is that if you ever change to a different server, your www record won't need to change if you update the A record for xyz.tk. The downside is that it requires 2 DNS requests to actually update resolve ...


3

This just might be the shortest answer I have ever written... You need to create a CNAME record in your DNS that points www.xyz.tk to xyz.tk.


2

It sounds like you may have initially changed the NAMESERVERS which broke the Windows Exchange CNAME. If the domain is hosted on GoDaddy then you need to access the DNS records, this is where the Windows Exchange CNAME is held. You should see an A record entry like A example.com 104.16.14.128 example.com will be your domain, the IP will be the GoDaddy ...


1

What you need to do is make a temporary subdomain using an A record pointed to the new shared server. Call it something like testing.example.com and point it to the new servers IP. Then ftp in, open or create an .htaccess, and point the request to whatever folder it needs to run using something like following. We will assume for this example that it's a ...


0

Are you using your own SSL, an SSL on Cloudflare, or both? Is the page not found message within your app, a cPanel master or default server 404, or something else like a standard unpretty browser 404? If you are seeing your default hosting provider or default cPanel 404 page, it hints that something went awry when the subdomain was set up, the local SSL ...


0

SSL must be enabled for every domain/subdomain required individually in cPanel. If you have moved your WHMCS installation to another domain, it is likely that you will need to regenerate the CSR/Key and request a new certificate. Once you've done that, follow the usual procedure to set it up and enable SSL for your subdomain.


2

You seem to have 2 A records for example.com pointing to very different IP addresses, one of which is the one that www.example.com resolves to (which is the wrong one). My guess is that it's picking the first one that it finds!?


0

I worked as a network engineer during the earliest days of the Internet until I retired from that work. As well, I was a web host at one point and understand the original intent of having more than one DNS for hosting domain names. I am working off of older rules in this answer. Some of them may have been relaxed. In the very early days, it was not uncommon ...


1

Some hosts/registrars allow you to create NS records. You could then create a record like this: subdomain.domain.tld NS ns3.domain.tld This will delegate the request for the lookup to another nameserver. Naturally, passing that request will require contacting the nameservers of the primary domain, which is probably not something you want. To be honest ...


1

After much pulling-out-of-hair, I got this message today: I logged into my router to check the DNS settings like we discussed. I just happened to click on security and noticed the "firewall" box was checked. I un-checked the box, clicked save, opened a new tab and entered our domain. Eureka! our site opened right up! It was my router.


1

Don't mind, I solved it! It was enough add the define( 'NOBLOGREDIRECT', '' ); in wp-config.php right below the multisite rules! I managed to insert my website homepage between '' To explain it better: if you insert a url between the '', when an user goes to a not exsisting subdomain such hello.example.com, he'll be redirected to the url you inserted; ...


0

Yes, you can safely add entries to the hosts file. The only thing you might need to consider is that the entries may be erased if you update WHM/Cpanel.


1

You can't set nameservers and CNAME records. Go to Namecheap.com --> Manage Domains and click on the domain you want to manage. Then, go to All Host Records and change the settings to this.



Top 50 recent answers are included