Re: Dig and SOA record

From: Gerald J T Harrison <harrison_at_no.spam.please>
Date: Fri Oct 27 2006 - 10:34:40 CST

 
Sorry I should have explained it a bit more..

the serial number / set date is a number that gets bigger with time and
that number is used for all the dns servers to keep track what is the
newest record.

The refresh time is telling all the servers that they should check back
in x seconds for changes to the record. Normally set in time frames of a
few days to 2 weeks. If the domain is staying on a machine for a long
time and not moving or changing keep it high to keep dns traffic requests
down.

retry is used if the web link goes down on the request and start looking
back / look to other secondarys in x seconds..

expire is the time you set that dns servers have to come back to refresh
the record.

ttl is time to live for broadcast of when you set the record in 1 or
something like that.

There are books and other web sites on bind that give a better
explaination than mine..

Gerald

On Fri, 27 Oct 2006, Gerald J T Harrison wrote:

> On Fri, 27 Oct 2006, Steven Kurylo wrote:
>
> > I've been searching around trying to find what the all the values mean
> > when dig returns an SOA record. Specifically I'm looking for the zone
> > refresh time.
> >
> > $ dig -t soa google.com
> > google.com. 86400 IN SOA ns1.google.com.
> > dns-admin.google.com. 2006102401 < date of record set
> 7200 < refresh in sec
> 1800 < retry
> 1038800 < expire
> 60 < default ttl (time to live)
>
> be careful of serial number/ set date...
> >
> > Is 2006102401 the serial number? Is 7200 the refresh time? Is 1800
> > the retry time? Making the last two the expire and minimum times?
> >
> > Thanks for any clarifications.
> >
> >
>
>
Received on Fri Oct 27 10:35:15 2006

This archive was generated by hypermail 2.1.8 : Fri Oct 27 2006 - 10:35:23 CST