Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 214
  • Last Modified:

DNS issues getting errors from dnsreport.com

DNS Report from dnsreport.com is showing:

      Open DNS servers   <-- failed
        Mismatched glue      <-- warning
        No NS A records at nameservers   <-- failed
        Lame nameservers  <-- failed



How do I correct this?

-J

0
jbrashear72
Asked:
jbrashear72
  • 2
  • 2
1 Solution
 
Cyclops3590Commented:
Can you provide the detail information that was in the right hand side for those to give us a better idea why it got the grade it did.

Open DNS - just means it accepts queries for zones its not authorized for - should say their in recursive state though
No NS A records at nameservers - could be an issue, but simple to fix
lame nameservers -could be an issue, and a little harder to fix

however more information would be appreciated.
0
 
m1tk4Commented:
Better yet, post your domain name.
0
 
jbrashear72Author Commented:
Lame nameservers
ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
64.191.69.86
204.15.135.34


No NS A records at nameservers
WARNING: Your nameservers do not include any corresponding A records when asked for your NS records. They probably are not returning the A records when asked, which can prevent some other DNS servers from contacting your DNS servers. They should do this if they are authoritative for those A records. The problem record(s) are:
Nameserver 64.191.69.86 did not provide IPs for all NS records (but did provide at least one)

http://www.dnsreport.com/tools/dnsreport.ch?domain=nocbank.net
0
 
m1tk4Commented:
"No NS A records at nameservers" - means you have name servers defined with NS records -

ns1.nocbank.net.
ns2.nocbank.net.
ns3.nocbank.net.

However you are missing the host records for ns1, ns2, ns3 in your domain:

ns1
0
 
jbrashear72Author Commented:
will that correct the lame server issue?
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now