Tag Info

New answers tagged

0

Sorry to say that to my knowledge this is only possible if you have two separate VPS with different IP addresses. As far as I know it is not possible to create two accounts in WHM with the same exact domain, but this is possible on two separate VPS because then you can point the DNS records for email to one VPS and the records for the www (website) to ...


0

Host your @ourdomain.com email on one cpanel account (let's call this cpanel #1) where the DNS points to for the domain name, and then setup an A record within cpanel #1 to point to the IP address used in cpanel #2. This way you can keep your email and web content on separate cpanel accounts, and your web visitors and email contacts won't know.


0

You actually don't have to switch to our nameservers when signing up through a panel option (that integration works via a CNAME).


0

Do you have access to the webhost manager interface? It's like cPanel on steroids. Or you could issue a 302 redirect to a different DNS resolver. Use a free or cheap DNS until cloudflare is open. Do you have any ability to set the nameserver host name itself? That might be a decent temporary fix.


0

It's so they know who actually administers to the site. In the event someone compromises a website theres someone at least kinda accountable.


1

Conclusion: you can't control which nameservers CloudFlare assigns to your domain name. The issue might be that CloudFlare reads the current DNS info for the domain while adding it to their site, which is already with CloudFlare, so you might be forced to wait to update it with your DNS provider :-/ This is one of those tough lessons learned through ...


4

The email address is part of the SOA record. It's second value is the email address of the administrator. As a minimum, the zone file must specify the Start of Authority (SOA) record with the name of the authoritative master name server for the zone and the email address of someone responsible for management of the name server. The email address in the ...


0

I have realized that www.succeedonline.co.za does not yet redirect under the non-www site under the https protocall. It does however work fine under the http protocall. Here is an extract of my complete .htaccess file: RewriteOptions inherit RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] # add a trailing slash to /wp-admin RewriteRule ...


0

You could also take the approach of multiple rewrite rules. Replace example.com with your actual domain name. RewriteEngine On RewriteCond %{HTTPS} off # HTTPS is off! # Redirect to the secure canonical URL RewriteRule (.*) https://example.com/$1 [L,R=301] RewriteCond %{HTTP_HOST} !^example\.com$ [NC] # Host name is not correct! # (maybe it has a www?) ...


1

Not sure if this would encompass your goal completely, but this would turn http www mode into https non-www mode: RewriteEngine On RewriteCond %{HTTPS} off [OR] RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC] RewriteRule ^(.*)$ https://example.com/$1 [R=301,L] Then to redirect the whmcs to a new url, you can probably use a simple 301: Redirect 301 ...



Top 50 recent answers are included