18 Oct
2014
18 Oct
'14
9:50 a.m.
Hi all,
I'm new on KNOT, and has been running BIND for many years now and would
like to set up another master server to serve the domain
metropolitanbuntu.co.za on a different network based on Debian and Knot.
The Knot-DNS server its running fine:
root@ns1:/etc/knot# knotc status
OK
The metropolitanbuntu.co.za zone was defined in the knot.conf file,
just simple definition:
zones {
# This is a default directory to place slave zone files, journals etc.
# default: ${localstatedir}/lib/knot, configured with --with-storage
storage "/var/lib/knot";
#
# Example master zone
# example.com {
# file "/etc/knot/example.com.zone";
# xfr-out slave0;
# notify-out slave0;
# }
#
# Example slave zone
# example.net {
# file "/var/lib/knot/example.net.zone
# xfr-in master0;
# notify-in master0;
# }
metropolitanbuntu.co.za {
file "/var/lib/knot/metropolitanbuntu.co.za.zone";
}
}
After ran:
root@ns1:/etc/knot# knotc -c knot.conf reload
OK
And checked the Syslog:
root@ns1:/etc/knot# grep knot /var/log/syslog
Oct 18 09:33:23 ns1 knotd[414]: info: remote control, received command
'refresh'
Oct 18 09:33:47 ns1 knotd[414]: info: remote control, received command
'reload'
Oct 18 09:33:47 ns1 knotd[414]: info: reloading configuration
Oct 18 09:33:47 ns1 knotd[414]: info: [metropolitanbuntu.co.za] zone is
up-to-date, serial 0
Oct 18 09:33:47 ns1 knotd[414]: info: configuration reloaded
Oct 18 09:42:24 ns1 knotd[414]: info: remote control, received command
'status'
Oct 18 09:45:03 ns1 knotd[414]: info: remote control, received command
'reload'
Oct 18 09:45:03 ns1 knotd[414]: info: reloading configuration
Oct 18 09:45:03 ns1 knotd[414]: info: [metropolitanbuntu.co.za] zone is
up-to-date, serial 0
Oct 18 09:45:03 ns1 knotd[414]: info: configuration reloaded
The metropolitanbuntu.co.za zone look up to date.
My question is:
its the zone file looks like the BIND one?
do I have to create it, may be I missed the zone declaration in the Knot
manual?
It is possible to do the master to master replication from BIND to KNOT?
Thanks for your support.
--
--
Kind Regards
Eric Kom
Senior IT Manager - Metropolitan Schools
_________________________________________
/ You are scrupulously honest, frank, and \
| straightforward. Therefore you have few |
\ friends. /
-----------------------------------------
\
\
.--.
|o_o |
|:_/ |
// \ \
(| Kom | )
/'\_ _/`\
\___)=(___/
2 Hennie Van Till, White River, 1240
Tel: 013 750 2255 | Fax: 013 750 0105 | Cell: 078 879 1334
erickom(a)kom.za.net | erickom(a)metropolitancollege.co.za www.kom.za.net |
www.kom.za.org | www.erickom.co.za
Key fingerprint: 513E E91A C243 3020 8735 09BB 2DBC 5AD7 A9DA 1EF5
19 Oct
19 Oct
1:37 p.m.
Hello Eric,
thank you for giving Knot DNS a try.
its the zone file looks like the BIND one?
Knot DNS accepts zones in textual master files format (RFC 1035). So the
answer is yes, if you are using the zones in "text" format.
do I have to create it, may be I missed the zone
declaration in the Knot
manual?
With the posted configuration, you have to provide Knot DNS with
existing zone file. Just copy the zone file from BIND.
If you want to configure Knot DNS as a slave server (see bellow), you do
not need to provide zone file at all.
It is possible to do the master to master replication
from BIND to KNOT?
We do not have mechanism for master-master replication. But I think you
are looking for master-slave replication.
In fact, master and slave functionality is orthogonal: Master means that
your server is configured to allow outgoing zone transfers. Slave means
that your server pulls the zones from other master servers. And you can
also configure a server to act both as a master and slave.
So you will have to configure BIND to act as a master. This is done
using the `allow-transfer` zone config option.
And as for Knot DNS as a slave, check the `xfr-in` zone option. A well
described minimal example can be found in our documentation:
https://www.knot-dns.cz/static/documentation/html/configuration.html#slave-…
Best regards,
Jan
20 Oct
20 Oct
9:01 a.m.
On 2014/10/19 01:37 PM, Jan Včelák wrote:
Thanks
Thats easy! I will do so.
NO, I got an existing master server based
on BIND9.9 that served the
domain metropolitanbuntu.co.za with slaves and would like to deployed
another master on a different network based on KNOT; so I will like the
listed domain to have 2 masters, in the way that if any record changed
in master based on BIND, KNOT must be notified without manualy changed
the another master if possible.
Hello Eric,
thank you for giving Knot DNS a try.
You are welcome
its the zone
file looks like the BIND one?
Knot DNS accepts zones in textual master files format
(RFC 1035). So the
answer is yes, if you are using the zones in "text" format. do I have to
create it, may be I missed the zone declaration in the Knot
manual?
With the posted configuration, you have to provide Knot DNS with
existing zone file. Just copy the zone file from BIND. If you want to configure Knot DNS as a slave server
(see bellow), you do
not need to provide zone file at all.
Like with BIND, Great!
It is possible
to do the master to master replication from BIND to KNOT?
We do not have mechanism
for master-master replication. But I think you
are looking for master-slave replication. In fact, master and slave functionality is orthogonal:
Master means that
your server is configured to allow outgoing zone transfers. Slave means
that your server pulls the zones from other master servers. And you can
also configure a server to act both as a master and slave.
So you will have to configure BIND to act as a master. This is done
using the `allow-transfer` zone config option.
Yes
And as for Knot DNS as a slave, check the `xfr-in`
zone option. A well
described minimal example can be found in our documentation:
https://www.knot-dns.cz/static/documentation/html/configuration.html#slave-…
Best regards,
Jan
9:25 a.m.
Hi Eric,
On Monday 20 of October 2014 09:01:01 Eric Kom wrote:
NO, I got an existing master server based on BIND9.9 that served the
domain metropolitanbuntu.co.za with slaves and would like to deployed
another master on a different network based on KNOT; so I will like the
listed domain to have 2 masters, in the way that if any record changed
in master based on BIND, KNOT must be notified without manualy changed
the another master if possible.
If you want replication from BIND to Knot DNS, then it is a master-slave
replication. BIND is a master (allows outgoing zone transfers) and Knot DNS is
a slave (pulls zone from master).
But the Knot DNS server can also act as a master and allow outgoing transfers
for other DNS servers on your second network.
This is how a configuration for your Knot DNS server could look like:
remotes {
net0_bind { address 192.168.1.10@53; }
net1_slave1 { address 192.168.2.11@53; }
net1_slave2 { address 192.168.2.12@53; }
}
zones {
metropolitanbuntu.co.za {
# pull zone from BIND on the first network (act as a slave)
xfr-in net0_bind;
notify-in net0_bind;
# provide zone for slaves on the second network (act as a master)
xfr-out net1_slave1, net1_slave2;
notify-out net1_slave1, net1_slave2;
}
}
So yes - the Knot DNS server is a master, but just for the second network. In
relation to the BIND on the first network, it is slave.
If you wanted to sync changes between the BIND and the Knot DNS in both
directions, that would be master-master replication. And we do not support it.
It might work, but you will encounter problems with synchronization if you
perform changes on both servers simultaneously.
Jan
It is possible to do the master to master replication
from BIND to KNOT?
We do not have mechanism for master-master replication. But I think you
are looking for master-slave replication.
4155
days inactive
4157
days old
3 comments
2 participants
participants (2)
-
Eric Kom -
Jan Včelák