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.
Related
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 have been given a task to integrate Active Directory in order to authenticate users and manage group policies. My end-goal is to allow users to enroll their devices (Mac and PC) into Active Directory using their company email address (ie. bob#example.com).
Currently, our company uses Godaddy to manage our DNS for our TLD (example.com). I have used a subdomain to allow public access to our domain controller (dc.example.com - Windows Server 2019). Now, because I've made the Domain Controller a subdomain of example.com, when I create an AD user, I can only register them in the dc.example.com namespace. Rather, I want users to be able to login using the top-level domain example.com.
I have been reading up on domain naming best-practices and everything tells me to use a subdomain rather than duplicating the root domain name. I have actually done the latter... and it works. However, it creates conflicts when I am trying to register Mac computers to Active directory. I don't know why.
I dont want to move away from Godaddy since we have many records stored there, but there MUST be an easier way to do this?
I have a website "example.com" with email user "anyname". I also have a domain name "other.com" with zone records pointing to "example.com". if I email "anyname#other.com" I get either a user not found or a relay not allowed message.
I have found no way to modify "other.com"s MX records to allow this.
I have also played with mod rewrite to no good effect.
I have created a new account on WHM and given it my domain name as the name. I then got the 2 name servers used by every site on my WHM server and inserted them into the Nameserver fields on the my registrars site. Is that all I have to do?
I know it sometimes takes a while for the domain name to perpetrate but when I type in the url it says it still parked. Is this ok?
Actually it seems what I've done is correct. The domain name did propagate eventually
A domain name that we have is using google mail as its backend, but its not hosted anywhere (no website). How can I, through the registrar interface (I'm using 1&1), redirect ppl who type in http://mail.example.com to http://mail.google.com/a/example.com ?
I can create a subdomain and set its DNS/CNAME, but what do I put where? Also, if I make this change will it affect the existing mail delivery (for which everything is running fine presently).
It turns out it wasn't that tough... and the instructions are part of Google itself:
Dashboard -> Service settings: Email -> General:Web address -> Change URL
https://www.google.com/a/cpanel/example.com/CustomUrl?s=mail
Changing CNAME record
To use the custom URL mail.example.com, you must change the CNAME record with your domain host.
Sign in to oneandone.
Navigate to your DNS Management page. The location and name
of this page will vary by host, but
can generally be found in Domain
Management or Advanced Settings.
Find the CNAME settings and enter the following as the CNAME value
or alias:
mail
Set the CNAME destination to the following address:
ghs.googlehosted.com
Save changes with your domain host and click "I've completed
these steps" below.
You cannot redirect to a path (such as /a/example.com) using only DNS. DNS CNAME records can make mail.example.com/foo effectively point to mail.google.com/foo, but something more sophisticated will require HTTP redirects. This means you need someone hosting your web page for this to work.
Sorry.
If your registrar offers an "HTTP Redirect" option, you can use that. Some registrars do. If you use this, they're effectively running a minimal web server for you. Note that this may break SSL when users access your page via https://example.com.
Mail delivery is via MX records, which won't be affected by changes to other types of record (so long as you don't interfere with the DNS records for the domain's mail servers).