- Newest
- Most votes
- Most comments
I am running the DNS on the server using BIND.
Yes I am just using siteground as the domain registrar and pointing the nameservers on their website to this new nameserver, we already have three other name servers that we run pointed to the domain but this one isn't working.
This is the error we are getting from siteground when trying to add the nameserver.
I don't know if Amazon has some kind of setting I need to adjust in order to use this server for DNS instead of Amazon's DNS.
Your question seems to be a bit scattered.
You say that you are going to use the server for DNS and FTP.
You say that you are using VirtualMin -- a web hosting control panel.
You say that you are trying to add the server to SiteGround which appears to be a web hosting provider.
What is missing to me are the details. Are you actually running DNS on the server? Bind or Unbound or some other DNS server?
If you are running DNS on the server are you just using SiteGround to update the name servers for your registered domain? Perhaps of your intent would help us understand and help you. Also perhaps some screenshots of actual errors?
I have been talking with SiteGround support and they swear up and down that Amazon has to register the nameserver on their end but since we don't use Amazon Route 53 or any Amazon DNS services do you think this is true?
Relevant content
- asked 10 months ago
- Accepted Answerasked 2 years ago
- asked 8 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 5 months ago
If you are running BIND on the server, there is nothing on the AWS side that you need to adjust (you are not using Route 53). I would suggest checking your Security Group to make sure that both tcp/udp port 53 are open.
The wording around Registry makes me wonder if you need to add the server to a registry of some sort on the SiteGround side before adding as a name server for the domain.
As long and you can successfully do DNS lookups (dig or nslookup) against the IP of your server, the I think the issue would be on the SiteGround side.
Hope this helps!
I have been talking with SiteGround support and they swear up and down that Amazon has to register the nameserver on their end but since we don't use Amazon Route 53 or any Amazon DNS services do you think this is true?