When i go to https://toolbox.googleapps.com/apps/checkmx/check?domain=domain.com
I get this error
All name servers should resolve to IP addresses.
Name servers that don't resolve reliably greatly reduce your domain's robustness. Only one NS IP
i checked my domain NS and everything seems to be fine
another issue : this domain MX records Point to Google, i have an admin console account,
for some reason some emails sent by hotmail from specific areas can't reach my inbox and they can't receive my mails as well
PLEASE Help
Related
SO Gurus,
As part of our on-prem exchange upgrade we are planning on implementing DKIM signing. We have a bit of a unique setup and need some DNS help. Our internal domain is inside.maindomain.com and out external domain is maindomain.com.
Our internal DNS server is configured with a forward lookup zone for maindomain.com
Our ISP has DNS records pointing MX to our internal exchange server and also Autodiscover.
Everything is working as intended (has been for a long time) however there is confusion about where the DKIM TXT record with the key needs to be located. If we put the record out at our ISP then our internal lookup does not find it; if we put it internally on our DNS server then the mail server sees it and the outside world does not. Do we need to put it in both places? Or do we need some sort of A record pointing either out or in? Some guidance would be greatly appreciated.
Getting used to answering my own questions.... apparently the TXT record needs to exist both internally and externally. DKIM, DMARC and SPF all flowing correctly now.
We have several servers on AWS VPC, but all have a 'public' face via DNS, handled with Route53. The problem is that when one server looks up the address of another server via DNS, if the entry is an 'A' record, it gets the public IP, not the AWS 'private' IP, and transfers go via the external network address.
If on the other hand I configure the domain as a CNAME pointing the the AWS public DNS name, like this:
CNAME super.domain.com ec2-1-2-3-4.compute-1.amazonaws.com
then lookups from 'outside' the VPC get the real external IP address, and lookups from 'inside' get the local 10.x.x.x address. This is exactly as I want it. Now the problem comes that these servers need to send mail, and pretty much everyone (mailgun, mandrill, etc.) requires SPF and DKIM records. But you can't mix those TXT records with a CNAME.
I know I could use /etc/hosts files on the servers to pre-empt the DNS lookup and use A records, but there are 14 servers and growing, and every time one of them is restarted, I'd have to update all the hosts files - seems like a recipe for messing things up.
My question is this: Is there a way to set up AWS Route53 so I can take advantage of the automatic internal/external resolution of the Amazon public DNS name, and still provide effective SPF and DKIM records? I did ask this on the AWS forum, but didn't get any help there...
Mailgun is probably closest, in that you can use a subdomain for the SPK/DKIM records (e.g. mg.super.domain.com), which then doesn't clash with the CNAME records. But then you hit this problem, the solution to which appears to be an A record, and I'm back to having to maintain many records when the instance IP addresses change!
So I am trying to set up name servers for my cPanel so when my clients point their domain to ns1.mydomain.com and ns2.mydomain.com their domain will work.
I have my A records NS1 and NS2 pointed to two different IPs on my server (the ones that get assigned when I click assign IP address.
As shown in the image here: http://prntscr.com/8vui67
Although the records don't seem to be working for my clients.
Here is my "show ip address usage"
http://prntscr.com/8vuikz
The name servers don't seem to be displayed here ( is that a problem ).
Sorry for what seems like a noob question, I have been working at this for several hours and I just keep running in circles.
I really appreciate the help.
Please make sure that you have completed the following steps:
[1] Assigned IPs to nameservers from WHM (From screen capture, it seems you already did it)
[2] Register your private nameservers from your registrar where your domain is registered.
[3] Add "A" records for ns1 and ns2 in the DNS zone of your domain (which is used for nameservers)
Now you should be able to use the nameservers without any problem.
EDIT:
Your domain nalhost.com is using your registrar's DNS so you will need to create A record in the DNS zone of your registrar. If you have already registered your private nameservers and add both A records, your nameservers should work. Are you receiving any error message while using your private nameservers?
I did the following steps but my domain was not getting resolved:
I created a zone (file) in Google Cloud -> Networking -> Cloud DNS using the right DNS name for the domain.
I put these NS as shown in Registrar Setup into my domain registrar:
ns-cloud-c1.googledomains.com
ns-cloud-c2.googledomains.com
ns-cloud-c3.googledomains.com
ns-cloud-c4.googledomains.com
I waited hours until the NS changes kicked in and verified in whois.
My domain was getting resolved.
Did I miss any other steps? I could not figure out so that I abandoned the Google Cloud DNS and went with my registrar's DNS and it is working now.
Make sure everything is spelled correctly.
i had trouble the other day. getting the domain to resolve while using google cloud services dns.
after waiting for about 30 hours, i double checked my work and found out that i had misspelled my domain name when i set up the dns zone.
usually the google dns entries resolve pretty quickly, especially if the domain is purchased from domains.google.com
the trailing . at the end has not been necessary for me. infact, when using domains.google.com, the trailing dot is automatically removed when entered as the custom dns-server.
All the NS you have listed doesn't have trailing . towards the end, as in
ns-cloud-c1.googledomains.com.
Would you be able to try updating the NS with your Registrar?
Have you already add a record (A record) to map the external IP address to your domain?
Your domain should be already working if you have all the records that are needed (and properly copied the NS record to your domain provider). However, for some time, you may need to wait for the propagation to change. See this link: https://cloud.google.com/dns/docs/overview#propagation_of_changes
In Google Cloud Platform, Cloud DNS has two requirements and I think you forgot the "A" record.
Requirements:
domain name from your domain name registrar.
IP address to point the A record of your zone. A valid IP address can be a server you already have running with an IP address you can point to.
To create an "A" record check below link:
https://cloud.google.com/dns/docs/quickstart#create_a_new_record
I have a domain (for example test.example.com) that I wish to forward to my own network for Active directory purposes. The network already has a static IP address, and a DNS server set up that is successfully handling requests for the Domain controller internally.
What I can't figure out is how to set it up so that I can connect to the Domain Controller from outside my Local network.
We use Names.co.uk for hosting, I've been messing around with the DNS settings for about a week, but the names will not resolve. can anybody explain what I need to dO?
FYI I've tried adding the SRV records to the names.co.uk DNS server, but they do not resolve back to the DC, I've also tried adding a NS record for the names.co.uk DNS server to get my DNS to resolve it, but that doesnt seem to work either!
DNS is resolves names using a hierarchy, with each level requiring NS record listing the low-levels. E.g. test.example.com: the 'com' zone has NS records for the 'example.com' nameservers and the 'example.com' zone has NS records for the 'test.example.com' nameservers.
So, not knowing your domain name, I can't check how it resolves. But I can say that to make it visible to the rest of the world, you need to have NS records created in the parent domain which point to your own nameservers (which should also contain NS records for your domain to pointing to themselves).