Plesk BIND DNS als Master

F

Flying Dutchman

New Member
Hallo,

Ich habe mir einen vserver bei Afahosting gemietet. Gerne würde ich die DNS Verwaltung von Plesk verwenden, was genau muss ich dafür einrichten?

Habe mir von einem anderen Server das Template angesehen und bei mir entsprechend die Nameserver von Afahosting eingetragen, sowie unter Transferzone die Ips der Nameserver.

Leider werden die DNS Einträge von Afahosting nicht übernommen. Laut der support muss was falsch konfiguriert sein.
Was habe ich vergessen/falsch gemacht?

Vielen Grüße
 
Last edited by a moderator:
Bei DNS-Einstellung der Domain auch auf Master umstellen nicht vergessen.

Wenn du den Nameserver dann neu startest, sollte er auch per IXFR die Daten an die Clients (Namserver des Anbieters) senden.
Schau mal ins Syslog.
 
Server Neustart hat leider nicht gewirkt.

Hier ist ein Auszug aus dem Logfile, beim aktivieren vom DNS für die Domäne:
Code: 
Apr 27 19:39:02 serv named[7823]: zone [DOMAIN].de/IN: (master) removed
Apr 27 19:39:02 serv named[7823]: reloading configuration succeeded
Apr 27 19:39:02 serv named[7823]: reloading zones succeeded
Apr 27 19:39:02 serv named[7823]: all zones loaded
Apr 27 19:39:02 serv named[7823]: running
Apr 27 19:39:07 serv dovecot: service=imap, user=info@[DOMAIN].de, ip=[52.174.33.
Apr 27 19:39:07 serv dovecot: service=imap, user=info@[DOMAIN].de, ip=[52.174.33.
Apr 27 19:39:07 serv dovecot: imap-login: Login: user=<info@[DOMAIN].de>, method=
Apr 27 19:39:08 serv dovecot: imap-login: Login: user=<info@[DOMAIN].de>, method=
Apr 27 19:39:17 serv plesk_saslauthd[22377]: select timeout, exiting
Apr 27 19:39:51 serv rndc[22578]: WARNING: key file (/etc/bind/rndc.key) exists, but using default configuration file (/etc/bind/rndc.conf)
Apr 27 19:39:51 serv named[7823]: received control channel command 'reload'
Apr 27 19:39:51 serv named[7823]: loading configuration from '/etc/named.conf'
Apr 27 19:39:51 serv named[7823]: GeoIP Country (IPv4) (type 1) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP Country (IPv6) (type 12) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP City (IPv4) (type 2) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP City (IPv4) (type 6) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP City (IPv6) (type 30) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP City (IPv6) (type 31) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP Region (type 3) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP Region (type 7) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP ISP (type 4) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP Org (type 5) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP AS (type 9) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP Domain (type 11) DB not available
Apr 27 19:39:51 serv named[7823]: GeoIP NetSpeed (type 10) DB not available
Apr 27 19:39:51 serv named[7823]: using default UDP/IPv4 port range: [1024, 65535]
Apr 27 19:39:51 serv named[7823]: using default UDP/IPv6 port range: [1024, 65535]
Apr 27 19:39:51 serv named[7823]: sizing zone task pool based on 3 zones
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 10.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 16.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 17.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 18.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 19.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 20.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 21.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 22.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 23.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 24.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 25.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 26.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 27.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 28.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 29.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 30.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 31.172.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 168.192.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 64.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 65.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 66.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 67.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 68.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 69.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 70.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 71.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 72.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 73.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 74.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 75.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 76.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 77.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 78.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 79.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 80.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 81.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv rndc[22578]: server reload successful
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 82.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 83.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 84.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 85.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 86.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 87.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 88.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 89.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 90.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 91.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 92.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 93.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 94.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 95.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 96.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 97.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 98.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 99.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 100.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 101.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 102.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 103.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 104.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 105.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 106.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 107.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 108.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 109.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 110.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 111.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 112.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 113.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 114.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 115.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 116.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 117.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 118.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 119.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 120.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 121.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 122.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 123.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 124.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 125.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 126.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 127.100.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 0.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 127.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 254.169.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: D.F.IP6.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 8.E.F.IP6.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 9.E.F.IP6.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: A.E.F.IP6.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: B.E.F.IP6.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Apr 27 19:39:51 serv named[7823]: automatic empty zone: EMPTY.AS112.ARPA
Apr 27 19:39:51 serv named[7823]: reloading configuration succeeded
Apr 27 19:39:51 serv named[7823]: reloading zones succeeded
Apr 27 19:39:51 serv named[7823]: zone [DOMAIN].de/IN: loaded serial 1524850791
Apr 27 19:39:51 serv named[7823]: all zones loaded
Apr 27 19:39:51 serv named[7823]: running
Apr 27 19:39:51 serv named[7823]: zone [DOMAIN].de/IN: sending notifies (serial 1524850791)
 
Eigentlich grept man nach Inhalten!
Was kommt bei:
service bind9 restart; tail -f /var/log/syslog | grep named

Dein Log sieht nicht so aus als habest du den Transfer an die Nameserver von Afahosting nach Außen aktiviert.

Es kann auch mal dauern, bis der extern NS was antwortet. Hatte ich vorhin bei hetzner auch mal.

Ansonsten prüfe mal deinem Plesk:
https://docs.plesk.com/de-DE/onyx/c...-eine-domain/plesk-als-masterdnsserver.65185/
https://docs.plesk.com/en-US/onyx/administrator-guide/dns/restricting-dns-zones-transfer.72219/
 
Last edited by a moderator:
Da kommt folgendes zurück:

Code: 
Apr 27 22:42:04 serv named[325]: received control channel command 'stop'
Apr 27 22:42:04 serv named[325]: shutting down: flushing changes
Apr 27 22:42:04 serv named[325]: stopping command channel on 127.0.0.1#953
Apr 27 22:42:04 serv named[325]: no longer listening on ::#53
Apr 27 22:42:04 serv named[325]: no longer listening on 127.0.0.1#53
Apr 27 22:42:04 serv named[325]: no longer listening on [SERVER IP]#53
Apr 27 22:42:04 serv named[325]: exiting
Apr 27 22:42:04 serv named[7154]: starting BIND 9.10.3-P4-Ubuntu <id:ebd72b3> -f -u bind -f -t /var/named/run-root -c /etc/named.conf
Apr 27 22:42:04 serv named[7154]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--libdir=/usr/lib/x86_64-linux-gnu' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--with-atf=no' '--enable-ipv6' '--enable-rrl' '--enable-filter-aaaa' '--enable-native-pkcs11' '--with-pkcs11=/usr/lib/x86_64-linux-gnu/softhsm/libsofthsm2.so' 'CFLAGS=-g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing -fno-delete-null-pointer-checks -DNO_VERSION_DATE' 'LDFLAGS=-Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -DDIG_SIGCHASE'
Apr 27 22:42:04 serv named[7154]: ----------------------------------------------------
Apr 27 22:42:04 serv named[7154]: BIND 9 is maintained by Internet Systems Consortium,
Apr 27 22:42:04 serv named[7154]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Apr 27 22:42:04 serv named[7154]: corporation.  Support and training for BIND 9 are
Apr 27 22:42:04 serv named[7154]: available at https://www.isc.org/support
Apr 27 22:42:04 serv named[7154]: ----------------------------------------------------
Apr 27 22:42:04 serv named[7154]: adjusted limit on open files from 4096 to 1048576
Apr 27 22:42:04 serv named[7154]: found 6 CPUs, using 6 worker threads
Apr 27 22:42:04 serv named[7154]: using 3 UDP listeners per interface
Apr 27 22:42:04 serv named[7154]: using up to 4096 sockets
Apr 27 22:42:04 serv named[7154]: loading configuration from '/etc/named.conf'
Apr 27 22:42:04 serv named[7154]: GeoIP Country (IPv4) (type 1) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP Country (IPv6) (type 12) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP City (IPv4) (type 2) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP City (IPv4) (type 6) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP City (IPv6) (type 30) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP City (IPv6) (type 31) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP Region (type 3) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP Region (type 7) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP ISP (type 4) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP Org (type 5) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP AS (type 9) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP Domain (type 11) DB not available
Apr 27 22:42:04 serv named[7154]: GeoIP NetSpeed (type 10) DB not available
Apr 27 22:42:04 serv named[7154]: using default UDP/IPv4 port range: [1024, 65535]
Apr 27 22:42:04 serv named[7154]: using default UDP/IPv6 port range: [1024, 65535]
Apr 27 22:42:04 serv named[7154]: listening on IPv6 interfaces, port 53
Apr 27 22:42:04 serv named[7154]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 27 22:42:04 serv named[7154]: listening on IPv4 interface venet0:0, [SERVER IP]#53
Apr 27 22:42:04 serv named[7154]: generating session key for dynamic DNS
Apr 27 22:42:04 serv named[7154]: sizing zone task pool based on 3 zones
Apr 27 22:42:04 serv named[7154]: set up managed keys zone for view _default, file 'managed-keys.bind'
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 10.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 16.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 17.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 18.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 19.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 20.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 21.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 22.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 23.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 24.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 25.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 26.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 27.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 28.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 29.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 30.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 31.172.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 168.192.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 64.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 65.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 66.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 67.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 68.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 69.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 70.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 71.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 72.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 73.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 74.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 75.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 76.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 77.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 78.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 79.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 80.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 81.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 82.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 83.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 84.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 85.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 86.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 87.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 88.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 89.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 90.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 91.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 92.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 93.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 94.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 95.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 96.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 97.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 98.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 99.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 100.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 101.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 102.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 103.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 104.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 105.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 106.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 107.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 108.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 109.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 110.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 111.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 112.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 113.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 114.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 115.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 116.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 117.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 118.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 119.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 120.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 121.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 122.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 123.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 124.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 125.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 126.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 127.100.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 0.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 127.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 254.169.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: D.F.IP6.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 8.E.F.IP6.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 9.E.F.IP6.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: A.E.F.IP6.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: B.E.F.IP6.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Apr 27 22:42:04 serv named[7154]: automatic empty zone: EMPTY.AS112.ARPA
Apr 27 22:42:04 serv named[7154]: command channel listening on 127.0.0.1#953
Apr 27 22:42:04 serv named[7154]: managed-keys-zone: loaded serial 0
Apr 27 22:42:04 serv named[7154]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
Apr 27 22:42:04 serv named[7154]: zone [DOMAIN].de/IN: loaded serial 2018042703
Apr 27 22:42:04 serv named[7154]: all zones loaded
Apr 27 22:42:04 serv named[7154]: running
Apr 27 22:42:04 serv named[7154]: zone [DOMAIN].de/IN: sending notifies (serial 2018042703)

Dein Log sieht nicht so aus als habest du den Transfer an die Nameserver von Afahosting nach Außen aktiviert.
Click to expand...

Das kann sein, leider ist mir nicht bekannt wo diese Einstellung gesetzt wird :confused:

Ansonsten scheinen die Einstellungen soweit nach der Dokumentation eingestellt zu sein. Lediglich der Haken bei "Von IETF und RIPE empfohlenes Seriennummernformat verwenden!" habe ich jetzt gesetzt.

Viele Grüße


Edit: Müssten die IPs der Nameserver von Alfahosting nicht im Log auftauchen?
 
Ja, es müsste nam maximal ein paar Minuten was kommen. Der Server sendet ja ein Notify nach Außen. Aber es kommt nix zurück vom DNS des Alfahosting.

Kann sein, dass eine Firewall was blockt. Oder dass Alfahosting gar kein Transfer zulässt.
 
Das die das nicht zulassen war auch meine Vermutung. Der support war sich da auch uneinig. Zum Schluss kam da nur noch das die dabei nicht helfen könnten, da ich ein unmanaged Server habe....

Wenn die Konfiguration soweit in Ordnung ungläubig sein sollte, melde ich mich da heute nochmal.

Vielen Dank für deine Hilfe
 
Unter Tools & Einstellungen → DNS-Template → Transferbeschränkungen-Template sind die internen Nameserver-IPs der Alfahosting-NS eingetragen?
Und bei Tools & Einstellungen → DNS-Template → DNS-Rekursionseinstellugen ist Localnets gewählt?
Und du hast auch 'Änderungen des DNS-Templates anwenden' betätigt?


Du kannst ja mit tcpdump mal prüfen, ob was von Außen reinkommt und in ein eigenes Log schreiben. Das kannst du dann nach der Alfahosting-IP greppen. Die Netzwerkschnittstelle steht in /etc/network/interfaces

tcpdump -s0 -lni NETZWERKSCHNITTSTELLE 'udp port 53' | tee dns.log

Sieht dann so aus wenns klappt und ich nach der IP des externen Slave greppe:
Code: 
~ # tcpdump -s0 -lni enp6s0 'udp port 53' | tee dns.log | grep 193.47.99.3
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp6s0, link-type EN10MB (Ethernet), capture size 262144 bytes
11:43:25.302894 IP 213.133.***.**.7527 > 193.47.99.3.53: 24879 notify [b2&3=0x2400] [1a] SOA? ********.de. (91)
11:43:25.303046 IP 213.133.***.**.7527 > 193.47.99.3.53: 53022 notify [b2&3=0x2400] [1a] SOA? ********.de. (126)
11:43:25.303077 IP 213.133.***.**.7527 > 193.47.99.3.53: 9442 notify [b2&3=0x2400] [1a] SOA? ********.de. (89)
11:43:25.303184 IP 213.133.***.**.7527 > 193.47.99.3.53: 9784 notify [b2&3=0x2400] [1a] SOA? ********.de. (106)
11:43:25.314411 IP 193.47.99.3.53 > 213.133.***.**.7527: 24879 notify*- 0/0/0 (31)
11:43:25.314430 IP 193.47.99.3.53 > 213.133.***.**.7527: 9442 notify*- 0/0/0 (35)
11:43:25.314611 IP 193.47.99.3.53 > 213.133.***.**.7527: 53022 notify*- 0/0/0 (40)
11:43:25.314624 IP 193.47.99.3.53 > 213.133.***.**.7527: 9784 notify*- 0/0/0 (43)
11:43:25.803001 IP 213.133.***.**.23423 > 193.47.99.3.53: 37560 notify [b2&3=0x2400] [1a] SOA? ********.de. (119)
11:43:25.814441 IP 193.47.99.3.53 > 213.133.***.**.23423: 37560 notify*- 0/0/0 (44)
 
Last edited by a moderator:
Die Einstellungen sind so gesetzt. Das DNS Template habe ich auch angewandt und gestern sicherheitshalber die Domain nochmal neu angelegt in Plesk.

Die Nameserver IPs habe ich mittels tracert [DOMAIN] und ping [cns1.alfahosting.info] gefunden.

Werde den Befehl heute gegen den Abend mal laufen lassen und hier posten, danke.
 
Vielleicht musst du auch im Domain-Robot was eintragen. Aber ich bin keine Alfahosting-Kundin. Ich muss jetzt passen und kann nicht mehr weiter helfen.
 
Der Domain ist direkt dem VPS zugeordnet und somit nicht im Domain-Robot konfigurierbar.

Habe nur eine abgespeckte DNS Editor.

Laut Support, dem ich meinen Plesk Konfiguration mitgeteilt habe, soll es ein Konfigurationsfehler sein. Ohne Hinweis wo oder was.

Ich bedanke mich vielmals und poste heute Abend noch das Ergebnis von deinem Befehl.
 
Bist du sicher, dass du mit deinem Server-Paket überhaupt den Alfahosting-NS so als Slave per Zonentransfer seitens deines vServers benutzen kannst? Wenn deren NS nicht als Slave läuft, wird er auch nicht antworten auf Transfers. Das solltest du mal erst beim Support abklären.
Doku/Hilfen auf deren Website ist ja grauenhaft mager.
 
GwenDragon said:
Bist du sicher, dass du mit deinem Server-Paket überhaupt den Alfahosting-NS so als Slave per Zonentransfer seitens deines vServers benutzen kannst?
Click to expand...

Laut Support soll das gehen, auch wenn die nicht sehr überzeugend geklungen haben. Habe denen das Problem genauso dargestellt wie hier, da wurde ich prompt mit dem Hinweis abgewimmelt, das die da nicht helfen können, da ich ein unmanaged server habe.

Habe tcpdump ein wenig laufen lassen. mit "grep notify" und "grep *nameserver ip*" finde ich keine Einzige Zeile.

Habe mein named.conf ein wenig angepasst um ein notify an den Nameserver zu erzwingen (indem ich bei "also-notify" die ips der Nameserver eingetragen habe.

Mit "grep *nameserver ip*" erhalte ich dann folgendes:
Code: 
15:05:13.310205 IP 89.22.***.***.37409 > 109.237.142.8.53: 35908 notify [b2&3=0x2400] [1a] SOA? [DOMAIN].de. (102)
15:05:13.325383 IP 109.237.142.8.53 > 89.22.***.***.37409: 35908 notify NotImp*- 0/0/0 (28)
15:05:13.806920 IP 89.22.***.***.60760 > 109.237.142.8.53: 5796 notify [b2&3=0x2400] [1a] SOA? 0.0.127.IN-ADDR.ARPA. (106)
15:05:13.822137 IP 109.237.142.8.53 > 89.22.***.***.60760: 5796 notify NotImp*- 0/0/0 (38)
15:05:14.507780 IP 89.22.***.***.30089 > 109.237.142.8.53: 51441 notify [b2&3=0x2400] [1a] SOA? [DOMAIN].de. (102)
15:05:14.523069 IP 109.237.142.8.53 > 89.22.***.***.30089: 51441 notify NotImp*- 0/0/0 (28)

(Meldungen sind von direkt nach start des Dienstes.)

Leider haben sich die DNS Einträge von Nameserver von Alfahosting nicht geändert...


Edit: Versteh ich das Log soweit richtig, das mein Server die Änderung der SOA bekannt gibt, die Server von Alfahosting dies aber ablehnen?
 
Last edited by a moderator:
Dein angesprochener DNS will/kann das nicht. Sagt doch die Response nach dem Notify.

RFC 1996 sagt zu Notimp:
3.12. If a NOTIFY request is received by a slave who does not
implement the NOTIFY opcode, it will respond with a NOTIMP
(unimplemented feature error) message. A master server who receives
such a NOTIMP should consider the NOTIFY transaction complete for
that slave.
Click to expand...

Nun ja. Muss du dich halt an Alfahosting wenden.
 
You must log in or register to reply here.
Back
Top