Dedicated Server Nameserver And Named DNS

I purchased a new dedicated server out of Canada and received my login and IPs. I added them, setup WHM, updated WHM to newest version along with PHP 5.25, Mysql 5.0 and set it up to the best of my knowledge and transferred all my accounts from my previous semi-dedicated WHM. I have my own nameservers with Tucows register and transferred the new IPs on Friday at 2:00 pm CST. It is now sunday at 6pm CST and they seem to have propagated i think, but DNSreports still show errors on lucentone.com and ns1.lucentone.com. I checked all files in /etc folder and even did the rndc fix for WHM and Restarted Bind.

i went back in after contacting datacenter to ask them to help me and they dont know what could be wrong. I have no managed support on my Box but i know some linux and CPanel but never setup DNS, IPs and a Cpanel from scratch install with the zone files, this was my first time. Frustrated with this whole thing and staying up until 4am trying to fix these problems for the past 2 days. i finally got fed up as all my customers accounts are down and decided to do another updating of WHM and found that now my Dig has authorative records, but still DNSrepot and others are showing still problems with my nameservers. There has to be something still wrong. I dont know if i have the localhost set correctly as i have also added a S01.lucentone.com for my server host.

Maybe this is the problem, but i have never done this before. Can anyone help me with this?

If anyone could help me, this would be much appreciated. i am about to pull my hair out. :-)

Here is my Dig now:; <<>> DiG 9.3.3rc2 <<>> lucentone.com @ns1.lucentone.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18477
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;lucentone.com. IN A

;; ANSWER SECTION:
lucentone.com. 400 IN A 206.53.55.246

;; AUTHORITY SECTION:
lucentone.com. 400 IN NS ns2.lucentone.com.
lucentone.com. 400 IN NS ns1.lucentone.com.

;; ADDITIONAL SECTION:
ns1.lucentone.com. 400 IN A 206.53.55.238
ns2.lucentone.com. 400 IN A 206.53.55.237

;; Query time: 0 msec
;; SERVER: 206.53.55.238#53(206.53.55.238)
;; WHEN: Sun Feb 10 17:49:44 2008
;; MSG SIZE rcvd: 115
-------------------------------------------------------------------
and here is my Dnsreport and dnsreport.com. Still shows problems, but most of them pass except nameservers:

FAILLame nameserversERROR: 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:
206.53.55.238
206.53.55.237
PASSMissing (stealth) nameserversOK. All 0 of your nameservers (as reported by your nameservers) are also listed at the parent servers.

FAILMissing nameservers 2ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns1.lucentone.com.
ns2.lucentone.com.

FAILStealth NS record leakageYour DNS servers leak stealth information in non-NS requests:

Stealth nameservers are leaked [D.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [E.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [F.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [G.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [H.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [I.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [J.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [K.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [L.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [M.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [A.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [B.ROOT-SERVERS.NET.]!
Stealth nameservers are leaked [C.ROOT-SERVERS.NET.]!

This can cause some serious problems (especially if there is a TTL discrepancy). If you must have stealth NS records (NS records listed at the authoritative DNS servers, but not the parent DNS servers), you should make sure that your DNS server does not leak the stealth NS records in response to other queries.
SOA FAILSOA RecordNo valid SOA record came back:
(root) is not lucentone.com.