Issues with AWS DNS
Hello Folks,
I believe I am having issues with Amazon's AWS DNS. I have installed the cPanel & WHM through the official AMI listed on the cPanel website. I have set up WHM though setup, everything as it should be.
I have confirmed that WHM has detected NAT 1:1, i have two elastic IP's assigned to this instance.
I have 4 DNS zones:
example.ca (domain, 52.39.xxx.xx)
liquid.example.ca (hostname, 52.39.xxx.x)
ns1.example.ca (nameserver 52.39.xxx.xx)
ns2.example.ca (nameserver 52.39.xxx.xx)
My ect/hosts file contains:
127.0.0.1 localhost localhost.localdomain
52.39.151.25 liquid.example.ca liquid
My etc/resolv.conf contains:
nameserver 8.8.8.8
nameserver 8.8.4.4
I cannot get the nameservers to resolve. I have checked intodns, and I believe that I am having a DNS problem.
Could someone please help me out :) Thank you so much in advance.
Regards,
MUNDA
-
Hi Mundaa As per I've understand, you are using Route 53 on AWS, correct? First at all from A registry entry in all of domains point to elastic IP server from EC2 instance, that how i see it's correct. In my opinion try this: Modify your /etc/hosts - erase 52.39.151.25 liquid.example.ca liquid - Add: your_IP_private(server) hostname When you change this, once your DNS points to 52.39.151.25 it will ask to IP_PRIVATE and this query to virtualhosts from CPANEL. Note that you need accounts in list on whm with site assigned. Hope this can help you 0 -
Incorrect - I am using my own DNS on this server. I changed the DNS software from BIND to NSD, and everything is working properly now... Does anyone have any idea why BIND would not work? Thanks guys! 0 -
Incorrect - I am using my own DNS on this server. I changed the DNS software from BIND to NSD, and everything is working properly now... Does anyone have any idea why BIND would not work?
Hello, Does the issue continue when switching back to Bind? The information you provided suggests it was a temporary issue with the DNS configuration file that switching to NSD may have addressed. Thank you.0
Please sign in to leave a comment.
Comments
3 comments