I have problem with domain validation of Cyrillic domains (.мкд), but only when SLD contains only numbers. I get error "Domain is not valid". WHMCS's domain validation file is encrypted. How to make hook to validate domain and "roundabout" encrypted WHMCS template file for domain validation?
Related
My client recently purchased a new domain name and wants it to link to an interior page on the current website. Both domains are registered on the same account. The main site is currently hosted on a Media Temple Grid account and I see no option for "forwarding." There is an option to "Point the domain to another server." Not sure if this is more of a DNS record change or an .htaccess redirect?
The main website is: fairmountstrings.com
The new domain name that needs routing is: fairmountstringquartet.org
The interior page that I'm trying to route to is: fairmountstrings.com/concerts/fairmount-string-quartet/
I selected "Point the domain to another server" which made the DNS for fairmountstringquartet.org the same as the main website. I then tried multiple different redirects in the .htaccess file that's on the root of the server but nothing seems to be working.
I was playing with Front Door and did set up a custom domain.
This domain is a Subdomain-delegations to my Azure subscription. Meaning for the domain myCompany.com I do not have access to the DNS settings, but the admin of myCompany set a delegation of sub.myCompany.com to a DNS zone in my Azure subscription. So I have a zone sub.myCompany.com in my account. Meaning I can only create A/Alias for sub.myCompany.com which I set to be an alias of my front-door.
This did work fine and I added the subdomain to my front-door and everything worked fine including using a SSL certificate from my KeyVault.
During playing around I tried using managed certificates and enabled that on the subdomain. And now the domain is stuck at "Domain validation" since a few days:
And I can't change this back because this results in the following error:
Failed to update the custom https configuration
Failed to update the custom https configuration for the frontend host '...'. Error: The requested operation cannot be executed on the entity in the current state.
How can I cancel that state to set it back to my KeyVault certificate?
I guess as this is not a CNAME-mapping it did fall back to e-mail verification and as the TLD is not under my control the mail got lost at the company managing the TLD. I do not have a direct contact with that company as I'm a subcontractor to the TLD's company and that company is also not managing the main domain on their own so it is not that easy to get ahold of whomever could have received that mail. And as the KeyVault certificate was working fine I just want to switch back to that...
I also had the problem that the domain validation was still not completed after many days.
I then opened a ticket in Azure and then the process was terminated in the backend. After that I was able to start the domain validation again and then it worked within 1 hour with the certificate
I created a site with Hugo and I hosted it as a gitlab page.
To assign my custom domain I followed the instructions of this document of gitlab.
I created three DNS records:
one of type A with name # and value 35.185.44.232;
one of type TXT with name # and value _gitlab-pages-verification ... for the verification of the ownership of the domain;
one of type A with name www and value 35.185.44.232.
If I access the site using the address https://example.com everything works normally; but if I log in using the triple W (www.example.com) I get from gitlab the error message 401 You don't have permission to access the resource. The resource that you are attempting to access is protected and you don't have the necessary permissions to view it.
How can I correct it?
Try a CNAME instead of a second A record for your WWW. subdomain. Having two A records - one that points to your naked domain and one that points to your WWW-domain is either causing redirect error or simply does not exist since it, as your origin's subdomain, must exist as a separate entity on GitLab OR you can not concern yourself with it by using a CNAME record as I previously recommended and using a directory-style (as opposed to a subdomain-style) setup for your site. Each has its own benefits as well as drawbacks. I use the CNAME method and have a WWW-subdomain setup on GitLab in order for my sites to grant that extra bit of security and privacy to visitors that having a TLS cert installed on the WWW-subdomain offers.
I followed Quickstart: Add a custom domain name to Azure Active Directory to verify my custom domain but still experiencing difficulties. I owe a domain (something like www.example.com with the only difference is mine is not 'example') purchased at GoDaddy.com.
If I try to verify that domain and specify its name (in AAD portal) as www.example.com then I can successfully complete the verification, but if I use the name example.com (without www) - I am seeing an error saying
Unable to verify domain name. Ensure you have added the record above
at the registrar 'MyDomainNameIsHere.COM', and try again in a little
while.
I employed nslookup to make sure the TXT record was added, I also followed the section Troubleshooting, non of those 3 cases apply to me:
waited for few hours
made sure with nslookup that the dns record is
correct and exists
there is no existing domain with that name
Why does it work if I prefix it with www and doesn't without it? Do I need to make some changes at GoDaddy?
I need that custom verified domain to add AAD users associated with their emails at my domain, for instance, User1#example.com; User2#example.com and so on. That doesn't work when I verify the www option complaining that example.com is not verified domain but doesn't complain if I try to create a user User1#www.example.com and I cannot do that because there is no corresponding email address.
I just recently started my shopify store, as with all shopify sites my site has a X.myshopify.com url. However, I have a domain, X.com, that points at the same ip as the myshopify.com. The problem is that in search results (Google), the myshopify.com link is showing up instead of my main domain. Is there a way to fix this?
If you cant get shopify to redirect the shopify domain to the proper domain then ensure the shopify domain has canonical tags pointing to the proper domain and the proper domain should replace indexing in time.