Re: Nameserver Problem [more]

[David G. Miller (aka DaveAtFraud)]

Bob Goodwin - W2BOD  wrote:
> Ed Greshko wrote:
> > > Bob Goodwin - W2BOD wrote:
> > > > > Eureka!  It works, once I figured out that I had to do   'service 
> > > > > named restart'  each time I made a change, added an address to be 
> > > > > blocked.
> > >
> > > While that works, you really should be updating the serial number each 
> > > time you make a change to a zone file.  This is good practice to get 
> > > into if you decide to learn a bit more of bind.  I tend to use the 
> > > YYYYMMDDX format for my serial numbers.  Basically 10 changes/day....I 
> > > seldom do more.
> > >
> > > Then all you need do is "kill -1" on the named pid.
>
> I'm strictly an amateur at this computer game, there's a lot I don't 
> know, where is the serial number?
>
> Your comment/help is appreciated. Thanks.
>
> Bob Goodwin

Each of your zone files files should have a header that looks something 
like:

$TTL 1D
@               IN      SOA     ns3.davenjudy.org.      
root.fraud.davenjudy.org. (
                        2006110301 ; serial
                        3600 ; refresh
                        900 ; retry
                        1209600 ; expire
                        43200 ; default_ttl
                        )
;
                TXT     "Dave and Judy Miller's Network"
...

The line "2006110301 ; serial" is the serial number.  I'm using 
YYYYMMDDxx to generate my serial.  The idea is that nameservers 
recognize the serial as a means of overriding previous information.  
When you bump the serial other nameservers recognize that you have 
provided new information.

This particular example is from /var/named/chroot/var/named/davenjudy.org.

Cheers,
Dave

Nameserver Problem [more]

[Bob Goodwin]

David G. Miller wrote:
> Bob Goodwin - W2BOD  wrote:
> > Ed Greshko wrote:
> > > > Bob Goodwin - W2BOD wrote:
> > > > > > Eureka!  It works, once I figured out that I had to do
> > > >
> > > > 'service >> named restart'  each time I made a change, added an 
> > > > address to be >> blocked.
> > > >
> > > > While that works, you really should be updating the serial number
> > >
> > > each > time you make a change to a zone file.  This is good practice 
> > > to get > into if you decide to learn a bit more of bind.  I tend to 
> > > use the > YYYYMMDDX format for my serial numbers.  Basically 10 
> > > changes/day....I > seldom do more.
> > > > Then all you need do is "kill -1" on the named pid.
> >
> > I'm strictly an amateur at this computer game, there's a lot I don't 
> > know, where is the serial number?
> >
> > Your comment/help is appreciated. Thanks.
> >
> > Bob Goodwin
>
> Each of your zone files files should have a header that looks 
> something like:
>
> $TTL 1D
> @               IN      SOA     ns3.davenjudy.org.      
> root.fraud.davenjudy.org. (
>                        2006110301 ; serial
>                        3600 ; refresh
>                        900 ; retry
>                        1209600 ; expire
>                        43200 ; default_ttl
>                        )
> ;
>                TXT     "Dave and Judy Miller's Network"
> ...
>
> The line "2006110301 ; serial" is the serial number.  I'm using 
> YYYYMMDDxx to generate my serial.  The idea is that nameservers 
> recognize the serial as a means of overriding previous information.  
> When you bump the serial other nameservers recognize that you have 
> provided new information.
>
> This particular example is from 
> /var/named/chroot/var/named/davenjudy.org.
>
> Cheers,
> Dave

Thanks for another example.

Bob Goodwin