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?
Related
I've setup my personal website with github, figured out the DNS configs based on the following page. I used A records because those are used in Route53 configs and when I test my DNS routing for mydomainname.com with Route53 tool, I get the proper response.
i.e. the DNS returns me the required GitHub IPs as I configured. However, when I try to run dig mydomainname.com I get an empty response.
I'm confident that I've waited long enough for changes to propagate (probably more than two full days now) so what could be the issue here? Any advice on how to further troubleshoot the routing issues?
UPDATE:
Looked up my url's who is data.
DNS Hosting works with 2 steps: configuring the dns servers to answer queries, and delegating the domain to them.
The first part you seem to have working: you've set up a Route 53 Zone, configured the records, and have successfully resolved them from one of the nameservers in the NS record Route 53 configurd for you when you created the zone.
The second step is essentially to tell your registrar that when the public attempt to look up the domain, they should be referred to the route 53 servers you configured. By adding these same dns servers from the NS record in the working, public route 53 zone, you will delegate dns on that domain to those servers.
You registered your domain on amazon so it created a route53 zone for you, with matching DNS servers in it. Either you removed this zone or created another one. That's fine to do, but each zone costs 50 cents a month, so get in the habit of removing ones that aren't working. You can create any number of route 53 zones to serve the same domain, but the ones you put in the registrar are the ones the public will use to resolve the domain.
Once whois mydomain.tld ( or a web equivalent, if whois isn't available in your environment, like from your screenshot) shows the same nameservers that you can successfully query against with dig, you're golden. It might take some time for the registrar's setting to propagate; in practice this is typically on the order of minutes.
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!
OK so I'm trying add a clients account to my whm and for some reason it won't point to my nameservers. I've already just had them buy a hosting plan with hostgator but for future clients I would like to have this problem solved. shouldn't I be able to change their NS to my nameservers?
There is an option of adding child name servers in domain control panel.
First you need to add your server's primary name server as a child name servers to the client's domain control panel and provide the IP address of your primary name servers. Now try adding your name servers as a client's name servers. This will fix the issue.
Example
You have a domain abc.com for which you have configured nameservers ns1.abc.com and ns2.abc.com.
STEP 1
Login to clients domain panel and add child name servers to ns1.abc.com and ns2.abc.com and point the IP Address of server where ns1.abc.com and ns2.abc.com are resolving and save it.
STEP 2
Now go to the name servers section and change value of client's name server as ns1.abc.com and ns2.abc.com. You will see this time you will be able to add the name-servers without any issue.
I have a domain registered at godaddy [www.example.com]. And i have a free hosting at Binhoster.
I want to point my domain to Binhoster's FTP server where my pages are hosted.
I googled this and I was instructed to change my nameservers of godaddy to Binhoster's nameserver, then add the FTP IP in the A-Record.
But I, without changing the nameservers, Added the A-Record to point to Binhoster's and added a custom domain at Binhoster's [www.example.com to point to public_html] and its working. I'm currently using my original nameserver. Then why is it instructed to change nameservers everywhere. Is it mandatory ??
You may want to reach out directly to Binhoster to see why they suggest to change your NS. This may be because the IP address could change. If an IP address changes and you control the DNS, you will need to be notified and subsequently update the A record IP, whereas if you pointed your NS the IP may be updated automatically at the host.
Ultimately, as long as you point your A record to the host, you should be fine.
Lets say that I purchased a new domain (somedomain.com) from a domain registar and I wanted to setup my own nameserver on a server that has two IP addresses.
First I buy the domain.
I get the server.
install BIND9.
I login to the server and prepare the DNS records for NS1.SOMEDOMAIN.COM and NS2.SOMEDOMAIN.COM.
Where do I set these up in BIND and how should I do it?
Next Step:
Go back to the domain registar and set the DNS to point to NS1.SOMEDOMAIN.COM and NS2.SOMEDOMAIN.COM.
Is it a bad thing if the domain that I am forwarding is pointed to its OWN nameserver domain? Should I change this? How does it know where NS1 and NS2 go when both subdomains are apart of the domain that is being forwarded to them?
Should I just use the DNS provided by my registar and make two CNAME record entries for NS1 and NS2 to point to the server ips of the newly created DNS server? Would this work?
Can anyone explain this process to me? Thanks.
Do add the following step which is crucial to using your name servers in the WHOIS record:
Step 5: Go back to your registrar (wherever you bought the domain in step 1) and create the special NameServer records in their administrative control panel; for example, on godaddy.com, you need to go to advanced > hosts and there you can set up ns1 to point to the IP address of your server (step 2).
You will need to do the same for ns2.
This will vary from registrar to registrar, consult their documentation or contact customer support.
Step 6: Update the WHOIS record to reflect your new nameservers.
Where do I set these up in BIND and how should I do it?
You would set these up in the domain's zone record, not unlike this:
yourdomain.com. IN SOA ns1.yourdomain.com. you.yourdomain.com. (
1032789388
10800
3600
604800
300 )
yourdomain.com. IN NS ns1.yourdomain.com.
yourdomain.com. IN NS ns2.yourdomain.com.
ns1.yourdomain.com. IN A xxx.xxx.xxx.xxx
ns2.yourdomain.com. IN A yyy.yyy.yyy.yyy
Is it a bad thing if the domain that I am forwarding is pointed to its OWN nameserver domain? Should I change this?
Running DNS from the same domain is fine.
How does it know where NS1 and NS2 go when both sub-domains are apart of the domain that is being forwarded to them?
See Step 5 above - your registrar handles this bit, registering your name servers and allowing them to participate in the 'net.
Should I just use the DNS provided by my registar and make two CNAME record entries for NS1 and NS2 to point to the server ips of the newly created DNS server? Would this work?
This would not work as you would still need to do Step 5; to be honest, I'm not sure what would happen if you did not serve the DNS for ns1 off of the same host.
Additional note:
While you CAN run one DNS server for both ns1 and ns2, it is not recommended.
Usually you want your secondary (slave) DNS server to be as far away as possible from your primary (master) DNS server... located in a different country is usually the best.
But, there is nothing technically preventing you from using two different IPs on the same physical hardware.