Transfers not working

[Joseph S D Yao]

On Wed, Mar 29, 2006 at 01:10:14PM -0800, Mikhael47 wrote:
> I have a Bind 9.2.1 server setup with another one as the slave.  If the
> refresh limit is hit and the serial number on the master is
> incremented, the transfer does not occur.
> 
> Here is what my zone file looks like
...
> @       IN      SOA     dns2.versaterm.com.  root.localhost (
...
> dns2    IN      NS      198.73.216.183
> @       IN      NS      198.73.216.183
> 
> @       IN      MX      10      smtp.versaterm.com
...
> dns2    IN      A       198.73.217.183

None of these have anything to do with zone transfers.  The entries in
named.conf would do that.  But, given the number of errors in just these
lines, one wonders what one might find in the named.conf file?

Also, and THIS IS VERY IMPORTANT: if your master copy is riddled with
errors, the name server holding the master copy will not claim to be
authoritative, and will not allow zone transfers of the error-ridden
file.

Do you want to say what the real zone name is, and what the real values
are?

Would you post the named.conf files, and what is shown in your logs when
'named' starts up or tries to re-load?

Here is what you should have in your zone.  Say it's example.com, and
you want your name servers to be "example.com" and "dns2.example.com".

$TTL 86400
@	IN SOA	example.com. hostmaster.example.com. ...

	IN NS	example.com.
	IN NS	dns2.example.com.

	IN MX	10 smtp.example.com.

	IN A	198.73.216.182
dns2	IN A	198.73.216.183
smtp	IN A	198.73.216.64
...

Note that the blank left-hand sides use the last left-hand side, namely,
"@".  You don't want an NS record with "dns2.example.com." in the left-
hand side, you want an NS record with "example.com." (which is the value
that "@" will have) in the left-hand side and "dns2.example.com." [note
the appended dot] in the right-hand side.

And the e-mail address should be a real, workable e-mail address.  Not
"root.localhost".

In the name server containing the master copy, which we will assume is
example.com, you should have something like this, assuming that the file
containing the above is "zone.example" in the default directory.

zone "example.com"	IN {
	type master;
	file "zone.example";
}

In the name server which maintains a copy of the zone that is slaved to
this master copy, which we will assume is dns2, you should have
something like this.

zone "example.com"	IN {
	type slave;
	file "zone.example";
	masters { 198.73.217.182; };
}

There are lots of other things you COULD have in your zone{} statements,
but these are the minimum.

-- 
Joe Yao
-----------------------------------------------------------------------
   This message is not an official statement of OSIS Center policies.