Hi,
Just moved to servermatrix and trying to setup nameservers on my server.
(Dual Xeon, Redhat with Cpanel and WHM).
I have registered the domain tcsnames.biz with godaddy.com and have registered ns1.tcsnames.biz and ns2.tcsnames.biz and set the corresponding ip's in the godaddy console.
I have created a zone in WHM called tcsnames.biz and it has the default ip address.I have created an A record of ns1.tcsnames.biz and given it the default ip and also created an A record for ns2.tcsnames.biz and given it the next ip in the range.
I have waited a couple of days for propogation but still dont get anywhere.
Can anyone do an NSLookup of tcsnames.biz and give me any clues where i am going wrong.
If i run DNS Report it gives me lots of errors including saying that my nameservers are lame.
Please can any body help as i have tried all the threads relating to this subject and havent had any luck.
Thanks.

I did a lookup and could see that you have zones set up for tcsnames.biz, ns1.tcsnames.biz and ns2.tcsnames.biz.

Possible problems I could see:
1) The zone for tcsnames.biz does not contain an A record, and thus seems to point nowhere.
2) Seens like ns2 is listed as NS2 (capitals) in all the zones.

I am not sure if either of the above could be causing your problems, but I would fix both issues if it was me

Your domain is not pointing to your server for some reason, is this your hostname and does it have a prefix i.e. sv1.tcsnames.biz?
All prefix such as this and ns1 etc require an A record pointing to the relevant IP, all in the dns zone for tcsnames.biz.
Have you got the nameservers in the whm>Edit setup file?

Hi,
I think that everything you mention is there,
If i use NSLOOKUP with my domain and IP, tcsnames.biz and 67.18.225.66
it reads ok (as far as i know, could anyone check), there is an A record according to lookup and yet if i go to DNS report.com i get loads of errors including your nameservers are lame?
Any ideas
Thanks

http://samspade.org/t/whois?a=tcsnames.biz...f-8&btnGo=Whois

Your domain is not resolving to your server, I would say this is a dns error