syncronizing 2 dns server (windows/linux)

[Mark Andrews]

> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
> I'm using gmail, no idea why it would be doing that.
> 
> Thanks for the info on $ORIGIN
> 
> Is all that stuff in a document somewhere? I feel like DNS is the least
> documented service, yet it runs the backend of Everything. *shrugs*

	Well the source comes with all the RFC's that cover the protocol
	these include the format of master files.  The Administrators
	Reference Manual (doc/arm) covered named's extentions to the master
	file format.  Then there is the book, "DNS and BIND", which covers
	DNS basics and how the administer named.

	There really is plenty of documentation.   Just about all questions
	here could be answered with "upgrade" and/or read the documentation.

	Mark

> On 9/24/05, Barry Margolin <barmar at alum.mit.edu> wrote:
> >
> > In article <dh2s2r$ptl$1 at sf1.isc.org>,
> > Josh Hyles <josh.maillists at gmail.com> wrote:
> >
> > > Content-Type: text/plain; charset=3DISO-8859-1
> > > Content-Transfer-Encoding: quoted-printable
> > > Content-Disposition: inline
> >
> > Why are the above header lines showing up in the body of your messages?
> > Is there something wrong with your mail program?
> >
> > > In my example, the one using @ doesn't have an origin, and none of the
> > line=3D
> > > s
> > > above the first origin have the domain on them, so how is that record
> > > functioning correctly?
> >
> > There's always an origin. It starts out as the zone name (from
> > named.conf), and you can use $ORIGIN to change it.
> >
> > --
> > Barry Margolin, barmar at alum.mit.edu
> > Arlington, MA
> > *** PLEASE post questions in newsgroups, not directly to me ***
> >
> >
> >
> 
> 
> 
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org