Skip to main content

DNS not found error only for main domain

Comments

5 comments

  • sktest123
    dig @ns1.domain.com domain.tld what does it shows
    0
  • cPanelMichael
    Hello, Do you have any custom entries added to the DNS zone for "domain.tld" yet? If not, does deleting this DNS zone and then creating it again make a difference? Thank you.
    0
  • DavidV17
    Thanks for the responses! Sorry to be slow replying.
    dig @ns1.domain.com domain.tld what does it shows

    Here's what I get for dig @ns1.domain.tld domain.tld ; (1 server found) ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6764 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;domain.tld. IN A ;; Query time: 1 msec ;; SERVER: [NS IP]#53(NS IP) ;; WHEN: Tue Nov 28 16:46:33 EST 2017 ;; MSG SIZE rcvd: 54 For comparison, here's what I get for dig @ns1.domain.tld a.domain.tld ; (1 server found) ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47353 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;a.domain.tld. IN A ;; ANSWER SECTION: a.domain.tld. 14400 IN A [CORRECT IP] ;; AUTHORITY SECTION: a.domain.tld. 86400 IN NS ns1.domain.tld. a.domain.tld. 86400 IN NS ns2.domain.tld. ;; ADDITIONAL SECTION: ns1.domain.tld. 14400 IN A [NS IP] ns2.domain.tld. 14400 IN A [NS IP] ;; Query time: 1 msec ;; SERVER: [NS IP]#53([NS IP]) ;; WHEN: Tue Nov 28 16:48:00 EST 2017 ;; MSG SIZE rcvd: 141 It's quite strange, because the zone files look identical in every way. It's just that domain.tld isn't getting served by the nameservers. I do have some custom DNS for domain.tld, but I'm going to delete it and then add it again, as @cPanelMichael suggested. I'll let you guys know if that helps.
    0
  • DavidV17
    Well, there you go. @cPanelMichael suggestion fixed it. When I deleted the domain.tld zone file and then added it again, the new zone file which cPanel generated included A records for ns1 and ns2. I had assumed those weren't needed because ns1.domain.tld and ns2.domain.tld already had their own, separate zone files, but apparently the A records needed to exist within domain.tld's zone file too. I assume adding the A records for ns1 and ns2 is what fixed it, but, regardless, the domain is now resolving properly. Thanks!
    0
  • cPanelMichael
    Hello, I'm glad to see it's now working well. Thank you for updating us with the outcome.
    0

Please sign in to leave a comment.