NS server coming up lame

55 msg	What is sysquery ?
57 msg	BIND 9.4.1-P1 compilation settings.
2 msg	Identifying and deleting unused DNS entries
1 msg	LISA '07 - Latest News and Top 5 Reasons to Attend
8 msg	Breaking up a class for delegation
24 msg	Problems with our migration from MS to BIND thi...
6 msg	rndc stats on SLES 10 (BIND 9.3.2)
2 msg	Rndc stats not showing correct figures
3 msg	Bind 9
3 msg	How to create my own RPM from RPM source?
2 msg	xfer-in.log errors
1 msg	Re: Views causing zone transfer problems? RESOLVED
4 msg	Views causing zone transfer problems?

NS server coming up lame
\ Ryan McCain (19 Sep 2007)
. \ Chris Buxton (19 Sep 2007)
. . \ Ryan McCain (19 Sep 2007)

2 msg	New version of Bind9 LDAP SDB driver - HOWTO?
3 msg	chaching is possible on dns-ldap?
2 msg	Reg : DNS Cache poisoning
3 msg	from nslookup's query
2 msg	log file flags...
4 msg	Performance issues

Subject:	NS server coming up lame
Group:	Bind-users
From:	Ryan McCain
Date:	19 Sep 2007

Per suggestions here I am attempting to get rid of the 2 $ORIGIN statements in my zone file.

When I check my domain from dnsstuff.com I get this error:

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:
199.248.209.34

..The only thing that changed was I commented out the 2 $ORIGIN statements and changed dss.state.la.us to @ in the SOA record.

Here is the zone file:
;$ORIGIN .
$TTL 3600 ; 1 hour
@ IN SOA dssns.dss.state.la.us. rmccain.dss.state.la.us (
2007091901 ; serial
1200 ; refresh (20 minutes)
600 ; retry (10 minutes)
1209600 ; expire (2 weeks)
3600 ; minimum (1 hour)
)
NS dssns.dss.state.la.us.
NS dssns2.dss.state.la.us.
A 205.172.49.49
MX 10 smtp-ext1.dss.state.la.us.
MX 20 smtp-ext2.dss.state.la.us.
;$ORIGIN dss.state.la.us.
acess A 205.172.49.23
acess-info A 205.172.49.23
acspoc A 205.172.49.9
<-SNIP->

Is there something wrong w/ my syntax?