DNS not working for main site.
- Thread starter angler
- Start date
nobaloney
NoBaloney Internet Svcs - In Memoriam †
You don't give us the name that's not resolving so this is only a guess:
1) Make sure the registry where you registered the domain points to two valid DSN servers.
2) Make sure those DNS servers contain valid records for the domain.
3) Make sure those records point DNS A resolution to the proper IP# on your server.
4) Be sure to check your domain resolution here.
Jeff
1) Make sure the registry where you registered the domain points to two valid DSN servers.
2) Make sure those DNS servers contain valid records for the domain.
3) Make sure those records point DNS A resolution to the proper IP# on your server.
4) Be sure to check your domain resolution here.
Jeff
Thanks for the reply. The domain name is pointed to the correct name servers. The nameservers are on DA and there is a zone for the domain. All the reocrds appear to be correct for the domain.
Using the DNS test site it says I have 1 or more lame name servers. It lists both of my name servers IP addresses as being lame.
It also says that both of my name servers are missing. " One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers."
For the domain thats not resolving there are A records pointing to the correct IP's. There are also NS records for the domain pointing to the correct ns1 and ns2 name servers.
Under Reseller panel > Name servers, the IP's and nameservers are assigned. All other domains on the server have no issue with DNS and run without errors on dnsreport. It is only the main domain on DA. The one that is setup under the User panel.
Using the DNS test site it says I have 1 or more lame name servers. It lists both of my name servers IP addresses as being lame.
It also says that both of my name servers are missing. " One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers."
For the domain thats not resolving there are A records pointing to the correct IP's. There are also NS records for the domain pointing to the correct ns1 and ns2 name servers.
Under Reseller panel > Name servers, the IP's and nameservers are assigned. All other domains on the server have no issue with DNS and run without errors on dnsreport. It is only the main domain on DA. The one that is setup under the User panel.
nobaloney
NoBaloney Internet Svcs - In Memoriam †
As I wrote previously, without the domain name information all I can do is guess.
I've already guessed.
Jeff
I've already guessed.
Jeff
It's a nameserver problem:
http://www.dnsreport.com/tools/dnsreport.ch?domain=cancunsystems.com
I don't know what the cause would be off hand. Something I read several years ago was that you might run into problems if your domain is also the domain of your nameservers. I don't know if that's fact or myth, I've never had that problem but I've never used Godaddy for nameserver setups...
http://www.dnsreport.com/tools/dnsreport.ch?domain=cancunsystems.com
I don't know what the cause would be off hand. Something I read several years ago was that you might run into problems if your domain is also the domain of your nameservers. I don't know if that's fact or myth, I've never had that problem but I've never used Godaddy for nameserver setups...
Last edited:
nobaloney
NoBaloney Internet Svcs - In Memoriam †
These are the errors I see now:
One of your nameservers doesn't respond.
You don't have reverse DNS set up for your MX server IP#s. (note that you may not be able to fix this yourself; generally your upstream provider provides reverse DNS).
You don't have any records for mail.cancunsystems.com, though you list it in your MX record.
Since you're using zone-edit, and they tend to know what they're doing, the problem is most likely with the records you've set up rather than with your nameserver.
There shouldn't be any problem with a nameserver at the same domain; we do it with ns-one.net and you can read the DNS Report output here.
Jeff
One of your nameservers doesn't respond.
You don't have reverse DNS set up for your MX server IP#s. (note that you may not be able to fix this yourself; generally your upstream provider provides reverse DNS).
You don't have any records for mail.cancunsystems.com, though you list it in your MX record.
Since you're using zone-edit, and they tend to know what they're doing, the problem is most likely with the records you've set up rather than with your nameserver.
There shouldn't be any problem with a nameserver at the same domain; we do it with ns-one.net and you can read the DNS Report output here.
Jeff
Here is the info from DA on the domain:
cancunsystems.com. A 69.57.146.43
ftp A 69.57.146.43
localhost A 127.0.0.1
mail A 69.57.146.43
ns1.cancunsystems.com. A 69.57.146.43
ns2.cancunsystems.com. A 69.57.146.155
ns2.cancunsystems.com. A pop 14400 IN A 69.57.146.43
www A 69.57.146.43
cancunsystems.com. NS ns1.cancunsystems.com.
cancunsystems.com. NS ns2.cancunsystems.com.
mail MX 10
cancunsystems.com. TXT "v=spf1 a mx ip4:69.57.146.43 ?all"
Does this look right? DA setup all this. All I did was create the account.
cancunsystems.com. A 69.57.146.43
ftp A 69.57.146.43
localhost A 127.0.0.1
mail A 69.57.146.43
ns1.cancunsystems.com. A 69.57.146.43
ns2.cancunsystems.com. A 69.57.146.155
ns2.cancunsystems.com. A pop 14400 IN A 69.57.146.43
www A 69.57.146.43
cancunsystems.com. NS ns1.cancunsystems.com.
cancunsystems.com. NS ns2.cancunsystems.com.
mail MX 10
cancunsystems.com. TXT "v=spf1 a mx ip4:69.57.146.43 ?all"
Does this look right? DA setup all this. All I did was create the account.
Last edited:
nobaloney
NoBaloney Internet Svcs - In Memoriam †
What's that second ns2 line; the one with pop right there in the middle?angler said:
Something's not right.
Anything wrong in a zone file will keep the zone file from loading.
Jeff
nobaloney
NoBaloney Internet Svcs - In Memoriam †
Since it was created by DA it could be a file corruption issue. You should make sure that your zone file has all the A records it's supposed to have.
Note that file corruption could also be an OS problem or a hard drive corruption problem.
Jeff
Note that file corruption could also be an OS problem or a hard drive corruption problem.
Jeff