Jump to content

How to configure DNS to work with WHMCS with complicated config


Recommended Posts

We have a vps using WHMCS. It’s set up for reselling domains (through enom) and reselling hosting (via cpanel) and we're trying to configure the DNS settings under Setup->Products/Services->Servers.


Our DNS situation is unique, and we’re looking for some guidance on how to configure it.


I’ve substituted example.com for our domain, and non-routable ip addressess for this post. However, the actual domain and IP’s are live and working now.



Our current setup is:


* RegistrationTek, our domain name registrar, where we purchased example.com. There are no zone records here. It specifies the following nameservers for example.com. The nameservers are at DnsMadeEasy.






* DnsMadeEasy, our DNS service. It has these zone records, among others:


A records

example.com, IP

vps.example.com, IP

backup.example.com, IP

ftp.example,com, IP


The example.com domain is hosted on our vps, within the 10.0.0.x IP range. Also hosted there is the vps.example.com domain


However, we have other sub-domains hosted on a completely different server, such as backup.example.com, on 192.168.1.x IP range.


Now, our vps has it’s own DNS records for example.com, IP, and vps.example.com, IP that point to itself. However, it does not currently have the backup.example.com or ftp.example.com records.


The vps nameservers are ns1.example.com, and ns2.example.com. These are not currently visible on the internet because they’re not referenced at DnsMadeEasy where are nameservers are.



So, we are trying to figure out how to configure the nameservers for WHMCS located at Setup->Products/Services->Servers.



If we use ns1.example.com and ns2.example.com, then we think it won’t work since those DNS servers are not visible on the internet.


So, should we instead transfer all the DNS records from dnsmadeeasy to the DNS on the vps (which is under the domain names ns1.example.com and ns2.example.com) and then change the nameservers at RegistrationTek for example.com to ns1.example.com and ns2.example.com? Then update the nameservers for WHMCS ns1.example.com and ns2.example.com?


My understanding is that there must be glue records on the vps DNS sever for this to work, since it hosts example.com and is also the DNS for example.com. How can I confirm the glue records are present, if that's the case.



Edited by BBLSystems
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated