1

I am a noob when it comes to Servers and Web hosting so this may be the main issue. I bought a domian name on godaddy.com here. I am using a server with limestone networks to host the DNS server. I added the Domain with all the credentials (I think). I have the two NS, the A, and two CNAME's www and ftp. I am still getting a "server DNS address could not be found."

here is a pic of my Domain settings enter image description here It has been over 48 hours since I added the domain and NS. I ran a DNSreport and I got three main errors.

No nameservers respond to queries via TCP. If no nameservers respond to TCP connections, this means that standard zone transfers (usually for slave DNS server replication) and most DNSSEC functions will not work. This can cause difficult to diagnose issues with those protocols. The nameservers that failed TCP queries are:

Nameserver SOAs do not agree on the serial number. This is bad because your nameservers may contain different resource record data and cause delays or misrouting of packets. It is possible that you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. The nameserver SOAs and their mismatched serial numbers are:

We were unable to connect to any of your WWW addresses listed. Users will be unable to access your site until this is resolved.

Could these be the issues? I have a CNAME for the www. so I don't know why its unable to connect. Where can I look to figure out what to do? I turned my firewall off and I got the same problem so that is not the issue.

Improve this question
18
  • Can you add screen shots of your DNS settings? Otherwise we are just guessing.
    – closetnoc
    Apr 6, 2016 at 23:18
  • @closetnoc yes sorry
    – codegeek511
    Apr 6, 2016 at 23:25
  • Create an A record on the root domain which points to your server, then set your CNAME for www., alternatively you could create an A record for WWW. instead of a CNAME. Your domain is using the nameservers, but your nameservers are not responding with your records.
    – Analog
    Apr 6, 2016 at 23:25
  • @Analog sorry this is the noob coming through, what is different about an A record on the root domain than what I have done?
    – codegeek511
    Apr 6, 2016 at 23:27
  • @codegeek511 remove the "@." so your main A record is just "livinghealth.tv" are you using a control panel to edit these records or are you editing the actual record file? The CNAME record points a name to another name, instead of an IP while an A record point to an IP address. For example you www. CNAME is getting it's answer from your root domain A record.
    – Analog
    Apr 6, 2016 at 23:31

1 Answer 1

Reset to default
0

This is just a formatting error.

Remove the "@." from your A record and it should work. You will have to wait for the changes to propagate (or flush your DNS cache).

Improve this answer
1
  • 1
    As a warning that may not apply here so please just take for future info... many times people who are setting up DNS records that are not sure of the process are often setting them up on the host when the registrar is the authority. I always recommend using the registrar. Fewer steps and a lot less confusion. Much easier to make work. You can I can get it done, no question. But for those who are not DNS familiar, then even if we walk them through the process, there will be major confusion the next time around. Cheers!!
    – closetnoc
    Apr 7, 2016 at 1:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.