NS server coming up lame
cbuxton at menandmice.com
Wed Sep 19 20:25:28 UTC 2007
I'm not seeing a problem right now. Did you fix it already, or was
there maybe a temporary condition on the slave server...?
Men & Mice
On Sep 19, 2007, at 9:28 AM, Ryan McCain wrote:
> 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:
> ..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 22.214.171.124
> MX 10 smtp-ext1.dss.state.la.us.
> MX 20 smtp-ext2.dss.state.la.us.
> ;$ORIGIN dss.state.la.us.
> acess A 126.96.36.199
> acess-info A 188.8.131.52
> acspoc A 184.108.40.206
> Is there something wrong w/ my syntax?
More information about the bind-users