NS server coming up lame

Ryan McCain Ryan.McCain at dss.state.la.us
Wed Sep 19 20:39:00 UTC 2007


I fixed it or it fixed itself.  The one thing I  noticed and changed was adding a trailing period after the contact email addy in the SOA record.

>>> On Wed, Sep 19, 2007 at  3:25 PM, in message
<562AAE48-4ADD-4E74-B8A5-3BCFAC694E33 at menandmice.com>, Chris Buxton
<cbuxton at menandmice.com> wrote: 
> I'm not seeing a problem right now. Did you fix it already, or was  
> there maybe a temporary condition on the slave server...?
> 
> Chris Buxton
> 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:
>> 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?
>>
>>
>>
>>
>>
>>



More information about the bind-users mailing list