Example: You have an own Master Nameserver

If you have your own Nameserver, you can use our infrastructure as Slave Nameserver set with different configurations. Our Nameserver set is also DNSSEC capable, if the Master NS is delivering proper DNSSEC data. You can state up to 8 Master NS IP addresses. Please make sure, that your Master Nameservers are in sync when using our KeyDNS als Slave NS.

Important: The following features are not working in combination with SLAVE zones:

SOA Updates

Parameters rr# addrr# delrr#

Commands QueryDNSZoneRRList and QueryDNSZoneSubdomainList

Web/Mailforwardings

DNSSEC

Import/ExportDNSZone

The following IP addresses are used to send notifies to and to allow transfer requests from.

European Set:

ns1-eu: 37.187.251.136 / 2001:41d0:c:388:37:187:251:136

ns2-eu: 37.187.168.234 / 2001:41d0:d:7ea:37:187:168:234

North America Set:

ns1-na.key-systems.net192.99.201.28 / 2607:5300:60:5e1c::

ns2-na.key-systems.net167.114.116.190 / 2607:5300:60:6bbe::

KeyDNS Unicast SlaveNS set for your Master NS

Command example to add a DNS zone with Unicast in KeyDNS for your Master NS. Note that the name service of your Master NS must be accessible regarding the relevant zones by our Slave NS.

Command

COMMAND = AddDNSZone
dnszone = yourdomain.TLD
MASTERIPADDRESS# = [IP]

KeyDNS Unicast SlaveNS set for your hidden Master NS

Command example to add a DNS zone with Unicast in KeyDNS for your hidden Master NS. Note that the name service of your Master NS must be accessible regarding the relevant zones by our Slave NS.

Command

COMMAND = AddDNSZone
dnszone = yourdomain.TLD
MASTERIPADDRESS# = [IP]

KeyDNS Anycast SlaveNS set for your Master NS

Command example to add a DNS zone with Anycast in KeyDNS for your Master NS. Note that the name service of your Master NS must be accessible regarding the relevant zones by our Slave NS.