Jax

Witam, mam pewien problem z domeną cyfrowyzasieg.pl. Domena wykupiona jest na home.pl i była zaparkowana na ich serwerach dns. Teraz postawiłem własny serwer DNS i chciałem wydelegować domenę na niego. Utworzyłem rekord SOA i niby wszystko działa bo strona chodzi. Problem w tym że na who.is mam No DNS records found. Na stronie www.whatsmydns.net również widać, że domena nie została rozpropagowana jak należy. Proszę o host -t soa cyfrowyzasieg.pl cyfrowyzasieg.pl has SOA record ns1.potel.com.pl. dawid.potel.pl. 2016072001 7200 540 604800 86400 dig cyfrowyzasieg.pl ;; ANSWER SECTION: cyfrowyzasieg.pl. 3600 IN A 91.231.20.206 ;; AUTHORITY SECTION: cyfrowyzasieg.pl. 3600 IN NS ns1.potel.com.pl. cyfrowyzasieg.pl. 3600 IN NS ns2.potel.com.pl. ;; ADDITIONAL SECTION: ns1.potel.com.pl. 3600 IN A 91.231.20.234 ns2.potel.com.pl. 3600 IN A 91.231.20.206 strefa dla domeny wygląda tak $TTL 3600 @ IN SOA ns1.potel.com.pl. dawid.potel.pl. ( 2016072001 ; serial, todays date + todays serial # 7200 ; refresh, seconds 540 ; retry, seconds 604800 ; expire, seconds 86400 ) ; minimum, seconds ; cyfrowyzasieg.pl. 3600 MX 10 mail.cyfrowyzasieg.pl. cyfrowyzasieg.pl. 3600 NS ns2.potel.com.pl. mail 3600 A 91.231.20.206 cyfrowyzasieg.pl. 3600 NS ns1.potel.com.pl. www 3600 A 91.231.20.206 cyfrowyzasieg.pl. 3600 A 91.231.20.206 i wpis w named.conf zone "cyfrowyzasieg.pl" { type master; file "/etc/bind/db.cyfrowyzasieg.pl"; allow-transfer { 91.231.20.206;}; notify yes; allow-query {any;}; Proszę o pomoc lub ewentualnie info czy wszystko jest ok i należy czekać na propagację dłużej. Dodam ze delegację domeny zrobiłem 3 dni temu.

Ok dzięki bardzo za info. Wpisałem sobie na kompie w ustawieniach karty sieciowej DNS 8.8.8.8 i wtedy strona nadal jest niewidoczna, rozumiem, że teraz muszę czekać ?

Rozumiem Kamikadze, że chodzi o ten wpis na czerwono "Recursive Queries" ?. Wstawiłem u siebie w options recursion no; pytanie czy to pomoże, bo dalej nic nie widać w internecie masakra, bo już kilka dni z tym walczę.

SPF wstawiony teraz jest ok. Mam ciągle problem z propagacją domeny i szukam przyczyny co jest nie tak. Na who.is ciągle mam "No DNS records found". named-checkzone localhost /etc/bind/pri.cyfrowyzasieg.eu zone localhost/IN: loaded serial 2016072311 OK

Zrobiłem mały test a mianowicie mam teraz domenę cyfrowyzasieg.eu postawiłem dwa serwery DNS na debianie jeezy, master i slave oba na publicznych numerach IP 91.231.20.206 i 91.231.20.207 deleguje domenę z home.pl na ns1.cyfrowyzasieg.eu oraz ns2.cyfrowyzasieg.eu podając dodatkowo numery ip ponieważ te dns-y nie mają żadnej domeny i będą przypisanej do domeny cyfrowyzasieg.eu. konfig dla ns1.cyfrowyzasieg.eu options { directory "/var/cache/bind"; // forwarders { // 0.0.0.0; // }; dnssec-validation auto; auth-nxdomain no; # conform to RFC1035 listen-on-v6 { none; }; allow-query {any;}; allow-transfer { 91.231.20.207;}; allow-recursion { any; }; allow-recursion-on { any; }; }; zone "cyfrowyzasieg.eu" { type master; allow-transfer {91.231.20.207;}; file "/etc/bind/pri.cyfrowyzasieg.eu"; }; $TTL 3600 @ IN SOA ns1.cyfrowyzasieg.eu. dawid.potel.pl. ( 2016072311 ; serial, todays date + todays serial # 3600 ; refresh, seconds 600 ; retry, seconds 1209600 ; expire, seconds 86400 ) ; minimum, seconds ; @ 86400 TXT "v=spf1 a mx ~all" @ 3600 MX 10 mail.cyfrowyzasieg.eu. @ 3600 A 91.231.20.206 @ 3600 NS ns1.cyfrowyzasieg.eu. @ 3600 NS ns2.cyfrowyzasieg.eu. ns1 86400 A 91.231.20.206 ns2 86400 A 91.231.20.207 mail 3600 A 91.231.20.206 www 3600 A 91.231.20.206 Log restartu bind na ns1 Jul 23 18:00:02 hosting named[28566]: starting BIND 9.9.5-9+deb8u6-Debian -4 -f -u bind Jul 23 18:00:02 hosting named[28566]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstate Jul 23 18:00:02 hosting named[28566]: ---------------------------------------------------- Jul 23 18:00:02 hosting named[28566]: BIND 9 is maintained by Internet Systems Consortium, Jul 23 18:00:02 hosting named[28566]: Inc. (ISC), a non-profit 501(c)(3) public-benefit Jul 23 18:00:02 hosting named[28566]: corporation. Support and training for BIND 9 are Jul 23 18:00:02 hosting named[28566]: available at https://www.isc.org/support Jul 23 18:00:02 hosting named[28566]: ---------------------------------------------------- Jul 23 18:00:02 hosting named[28566]: adjusted limit on open files from 4096 to 1048576 Jul 23 18:00:02 hosting named[28566]: found 1 CPU, using 1 worker thread Jul 23 18:00:02 hosting named[28566]: using 1 UDP listener per interface Jul 23 18:00:02 hosting named[28566]: using up to 4096 sockets Jul 23 18:00:02 hosting named[28566]: loading configuration from '/etc/bind/named.conf' Jul 23 18:00:02 hosting named[28566]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jul 23 18:00:02 hosting named[28566]: using default UDP/IPv4 port range: [1024, 65535] Jul 23 18:00:02 hosting named[28566]: using default UDP/IPv6 port range: [1024, 65535] Jul 23 18:00:02 hosting named[28566]: no IPv6 interfaces found Jul 23 18:00:02 hosting named[28566]: listening on IPv4 interface lo, 127.0.0.1#53 Jul 23 18:00:02 hosting named[28566]: listening on IPv4 interface eth0, 91.231.20.206#53 Jul 23 18:00:02 hosting named[28566]: generating session key for dynamic DNS Jul 23 18:00:02 hosting named[28566]: sizing zone task pool based on 8 zones Jul 23 18:00:02 hosting named[28566]: using built-in root key for view _default Jul 23 18:00:02 hosting named[28566]: set up managed keys zone for view _default, file 'managed-keys.bind' Jul 23 18:00:02 hosting named[28566]: automatic empty zone: 10.IN-ADDR.ARPA Jul 23 18:00:03 hosting named[28566]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jul 23 18:00:03 hosting named[28566]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jul 23 18:00:03 hosting named[28566]: 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 Jul 23 18:00:03 hosting named[28566]: 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 Jul 23 18:00:03 hosting named[28566]: automatic empty zone: D.F.IP6.ARPA Jul 23 18:00:03 hosting named[28566]: automatic empty zone: 8.E.F.IP6.ARPA Jul 23 18:00:03 hosting named[28566]: automatic empty zone: 9.E.F.IP6.ARPA Jul 23 18:00:03 hosting named[28566]: automatic empty zone: A.E.F.IP6.ARPA Jul 23 18:00:03 hosting named[28566]: automatic empty zone: B.E.F.IP6.ARPA Jul 23 18:00:03 hosting named[28566]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jul 23 18:00:03 hosting named[28566]: command channel listening on 127.0.0.1#953 Jul 23 18:00:03 hosting named[28566]: managed-keys-zone: loaded serial 7 Jul 23 18:00:03 hosting named[28566]: zone 0.in-addr.arpa/IN: loaded serial 1 Jul 23 18:00:03 hosting named[28566]: zone 127.in-addr.arpa/IN: loaded serial 1 Jul 23 18:00:03 hosting named[28566]: zone cyfrowyzasieg.eu/IN: 'cyfrowyzasieg.eu' found SPF/TXT record but no SPF/SPF record found, add matching type SPF re Jul 23 18:00:03 hosting named[28566]: zone cyfrowyzasieg.eu/IN: loaded serial 2016072311 Jul 23 18:00:03 hosting named[28566]: zone 255.in-addr.arpa/IN: loaded serial 1 Jul 23 18:00:03 hosting named[28566]: zone localhost/IN: loaded serial 2 Jul 23 18:00:03 hosting named[28566]: zone potel.com.pl/IN: loaded serial 2016072003 Jul 23 18:00:03 hosting named[28566]: zone cyfrowyzasieg.pl/IN: loaded serial 2016072002 Jul 23 18:00:03 hosting named[28566]: all zones loaded Jul 23 18:00:03 hosting named[28566]: running Jul 23 18:00:03 hosting named[28566]: zone cyfrowyzasieg.eu/IN: sending notifies (serial 2016072311) Jul 23 18:00:03 hosting named[28566]: zone potel.com.pl/IN: sending notifies (serial 2016072003) Jul 23 18:00:03 hosting named[28566]: zone cyfrowyzasieg.pl/IN: sending notifies (serial 2016072002) Jul 23 18:00:03 hosting named[28566]: client 91.231.20.207#37744 (cyfrowyzasieg.eu): transfer of 'cyfrowyzasieg.eu/IN': AXFR-style IXFR started Jul 23 18:00:03 hosting named[28566]: client 91.231.20.207#37744 (cyfrowyzasieg.eu): transfer of 'cyfrowyzasieg.eu/IN': AXFR-style IXFR ended konfig dla ns2.cyfrowyzasieg.eu options { directory "/var/cache/bind"; // forwarders { // 0.0.0.0; // }; dnssec-validation auto; auth-nxdomain no; # conform to RFC1035 listen-on-v6 { none; }; allow-query {any;}; }; zone "cyfrowyzasieg.eu" { type slave; masters {91.231.20.206;}; allow-transfer {91.231.20.206;}; file "/etc/bind/slave/sec.cyfrowyzasieg.eu"; }; po restarcie cała strefa zostaje skopiowana z mastera ponieważ tworzy mi się plik sec.cyfrowyzasieg.eu w katalogu slave logi restartu bind na ns2 Jul 23 18:07:05 ns2 named[17616]: starting BIND 9.9.5-9+deb8u6-Debian -4 -f -u bindJul 23 18:07:05 ns2 named[17616]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir= Jul 23 18:07:05 ns2 named[17616]: ---------------------------------------------------- Jul 23 18:07:05 ns2 named[17616]: BIND 9 is maintained by Internet Systems Consortium, Jul 23 18:07:05 ns2 named[17616]: Inc. (ISC), a non-profit 501(c)(3) public-benefit Jul 23 18:07:05 ns2 named[17616]: corporation. Support and training for BIND 9 are Jul 23 18:07:05 ns2 named[17616]: available at https://www.isc.org/support Jul 23 18:07:05 ns2 named[17616]: ---------------------------------------------------- Jul 23 18:07:05 ns2 named[17616]: adjusted limit on open files from 4096 to 1048576 Jul 23 18:07:05 ns2 named[17616]: found 1 CPU, using 1 worker thread Jul 23 18:07:05 ns2 named[17616]: using 1 UDP listener per interface Jul 23 18:07:05 ns2 named[17616]: using up to 4096 sockets Jul 23 18:07:05 ns2 named[17616]: loading configuration from '/etc/bind/named.conf' Jul 23 18:07:05 ns2 named[17616]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jul 23 18:07:05 ns2 named[17616]: using default UDP/IPv4 port range: [1024, 65535] Jul 23 18:07:05 ns2 named[17616]: using default UDP/IPv6 port range: [1024, 65535] Jul 23 18:07:05 ns2 named[17616]: no IPv6 interfaces found Jul 23 18:07:05 ns2 named[17616]: listening on IPv4 interface lo, 127.0.0.1#53 Jul 23 18:07:05 ns2 named[17616]: listening on IPv4 interface eth0, 91.231.20.207#53 Jul 23 18:07:05 ns2 named[17616]: generating session key for dynamic DNS Jul 23 18:07:05 ns2 named[17616]: sizing zone task pool based on 6 zones Jul 23 18:07:05 ns2 named[17616]: using built-in root key for view _default Jul 23 18:07:05 ns2 named[17616]: set up managed keys zone for view _default, file 'managed-keys.bind' Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: 10.IN-ADDR.ARPA Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: 16.172.IN-ADDR.ARPA Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jul 23 18:07:05 ns2 named[17616]: 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 Jul 23 18:07:05 ns2 named[17616]: 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 Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: D.F.IP6.ARPA Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: 8.E.F.IP6.ARPA Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: 9.E.F.IP6.ARPA Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: A.E.F.IP6.ARPA Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: B.E.F.IP6.ARPA Jul 23 18:07:05 ns2 named[17616]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jul 23 18:07:05 ns2 named[17616]: command channel listening on 127.0.0.1#953 Jul 23 18:07:05 ns2 named[17616]: managed-keys-zone: loaded serial 2 Jul 23 18:07:05 ns2 named[17616]: zone 0.in-addr.arpa/IN: loaded serial 1 Jul 23 18:07:05 ns2 named[17616]: zone 127.in-addr.arpa/IN: loaded serial 1 Jul 23 18:07:05 ns2 named[17616]: zone cyfrowyzasieg.eu/IN: loaded serial 2016072311 Jul 23 18:07:05 ns2 named[17616]: zone localhost/IN: loaded serial 2 Jul 23 18:07:05 ns2 named[17616]: zone 255.in-addr.arpa/IN: loaded serial 1 Jul 23 18:07:05 ns2 named[17616]: all zones loaded Jul 23 18:07:05 ns2 named[17616]: running Jul 23 18:07:05 ns2 named[17616]: zone cyfrowyzasieg.eu/IN: sending notifies (serial 2016072311) sprawdzenie pliku zone na ns1 named-checkzone localhost /etc/bind/pri.cyfrowyzasieg.eu zone localhost/IN: 'localhost' found SPF/TXT record but no SPF/SPF record found, add matching type SPF record zone localhost/IN: loaded serial 2016072311 OK do tego na ns1 i ns2 53/tcp open domain Możecie sprawdzić czy wszystko zrobiłem ok ?

Mam dwa osobne serwery dns, udp też nasłuchuje netstat -an | grep "udp " udp 0 0 91.231.20.234:40220 88.221.81.193:53 ESTABLISHED udp 0 0 91.231.20.235:53 0.0.0.0:* udp 0 0 91.231.20.234:53 0.0.0.0:* udp 0 0 91.231.20.234:21337 115.231.89.12:53 ESTABLISHED udp 0 0 0.0.0.0:111 0.0.0.0:* udp 0 0 127.0.0.1:630 0.0.0.0:* udp 0 0 0.0.0.0:49042 0.0.0.0:* udp 0 0 127.0.0.1:921 0.0.0.0:* udp 0 0 0.0.0.0:1022 0.0.0.0:*

Podbiłem serial i przeładowałem, podaje poniżej logi. Chociaż nie sądzę żeby to było to Nadal mam domenę nierozpropagowaną. Logi po restarcie Jul 22 12:41:04 ns named[29209]: starting BIND 9.8.4-rpz2+rl005.12-P1 -4 -u bind Jul 22 12:41:04 ns named[29209]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '-- Jul 22 12:41:04 ns named[29209]: ---------------------------------------------------- Jul 22 12:41:04 ns named[29209]: BIND 9 is maintained by Internet Systems Consortium, Jul 22 12:41:04 ns named[29209]: Inc. (ISC), a non-profit 501(c)(3) public-benefit. Jul 22 12:41:04 ns named[29209]: corporation. Support and training for BIND 9 are. Jul 22 12:41:04 ns named[29209]: available at https://www.isc.org/support Jul 22 12:41:04 ns named[29209]: ---------------------------------------------------- Jul 22 12:41:04 ns named[29209]: adjusted limit on open files from 4096 to 1048576 Jul 22 12:41:04 ns named[29209]: found 1 CPU, using 1 worker thread Jul 22 12:41:04 ns named[29209]: using up to 4096 sockets Jul 22 12:41:04 ns named[29209]: loading configuration from '/etc/bind/named.conf' Jul 22 12:41:04 ns named[29209]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jul 22 12:41:04 ns named[29209]: using default UDP/IPv4 port range: [1024, 65535] Jul 22 12:41:04 ns named[29209]: using default UDP/IPv6 port range: [1024, 65535] Jul 22 12:41:04 ns named[29209]: no IPv6 interfaces found Jul 22 12:41:04 ns named[29209]: listening on IPv4 interface eth0, 91.231.20.234#53 Jul 22 12:41:04 ns named[29209]: listening on IPv4 interface eth0:1, 91.231.20.235#53 Jul 22 12:41:04 ns named[29209]: generating session key for dynamic DNS Jul 22 12:41:04 ns named[29209]: sizing zone task pool based on 10 zones Jul 22 12:41:04 ns named[29209]: set up managed keys zone for view _default, file 'managed-keys.bind' Jul 22 12:41:04 ns named[29209]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones Jul 22 12:41:04 ns named[29209]: automatic empty zone: 254.169.IN-ADDR.ARPA Jul 22 12:41:04 ns named[29209]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Jul 22 12:41:04 ns named[29209]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jul 22 12:41:04 ns named[29209]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jul 22 12:41:04 ns named[29209]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jul 22 12:41:04 ns named[29209]: 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 Jul 22 12:41:04 ns named[29209]: 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 Jul 22 12:41:04 ns named[29209]: automatic empty zone: D.F.IP6.ARPA Jul 22 12:41:04 ns named[29209]: automatic empty zone: 8.E.F.IP6.ARPA Jul 22 12:41:04 ns named[29209]: automatic empty zone: 9.E.F.IP6.ARPA Jul 22 12:41:04 ns named[29209]: automatic empty zone: A.E.F.IP6.ARPA Jul 22 12:41:04 ns named[29209]: automatic empty zone: B.E.F.IP6.ARPA Jul 22 12:41:04 ns named[29209]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jul 22 12:41:05 ns named[29209]: command channel listening on 127.0.0.1#953 Jul 22 12:41:05 ns named[29209]: zone 0.in-addr.arpa/IN: loaded serial 1 Jul 22 12:41:05 ns named[29209]: zone 127.in-addr.arpa/IN: loaded serial 1 Jul 22 12:41:05 ns named[29209]: zone 255.in-addr.arpa/IN: loaded serial 1 Jul 22 12:41:05 ns named[29209]: zone 19.231.91.in-addr.arpa/IN: loaded serial 2013040401 Jul 22 12:41:05 ns named[29209]: zone 20.231.91.in-addr.arpa/IN: loaded serial 2013040401 Jul 22 12:41:05 ns named[29209]: zone 21.231.91.in-addr.arpa/IN: loaded serial 2016072002 Jul 22 12:41:05 ns named[29209]: zone localhost/IN: loaded serial 2 Jul 22 12:41:05 ns named[29209]: zone potel.com.pl/IN: loaded serial 2016072003 Jul 22 12:41:05 ns named[29209]: zone cyfrowyzasieg.pl/IN: loaded serial 2016072002 Jul 22 12:41:05 ns named[29209]: managed-keys-zone ./IN: loaded serial 0 Jul 22 12:41:05 ns named[29209]: running Jul 22 12:41:05 ns named[29209]: zone cyfrowyzasieg.pl/IN: sending notifies (serial 2016072002) Jul 22 12:41:05 ns named[29209]: zone potel.com.pl/IN: sending notifies (serial 2016072003) Jul 22 12:41:05 ns named[29209]: client 91.231.20.206#52930: transfer of 'cyfrowyzasieg.pl/IN': AXFR-style IXFR started Jul 22 12:41:05 ns named[29209]: client 91.231.20.206#52930: transfer of 'cyfrowyzasieg.pl/IN': AXFR-style IXFR ended Jul 22 12:41:46 ns named[29209]: success resolving 'goo.gl/A' (in 'goo.gl'?) after reducing the advertised EDNS UDP packet size to 512 octets Jul 22 12:41:59 ns named[29209]: success resolving 'alog.umeng.com/A' (in 'umeng.com'?) after reducing the advertised EDNS UDP packet size to 512 octets Jul 22 12:43:07 ns named[29209]: success resolving 'usa.ime.cootek.com/A' (in 'cootek.com'?) after reducing the advertised EDNS UDP packet size to 512 octets Jul 22 12:43:08 ns named[29209]: success resolving 'ns4.dnsv4.com/A' (in 'dnsv4.com'?) after reducing the advertised EDNS UDP packet size to 512 octets Jul 22 12:43:10 ns named[29209]: success resolving 'ns3.dnsv4.com/A' (in 'dnsv4.com'?) after reducing the advertised EDNS UDP packet size to 512 octets Jul 22 12:43:22 ns named[29209]: success resolving 'sis.jpush.io/A' (in 'jpush.io'?) after disabling EDNS netstat -an | grep "LISTEN " tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:59539 0.0.0.0:* LISTEN tcp 0 0 91.231.20.235:53 0.0.0.0:* LISTEN tcp 0 0 91.231.20.234:53 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:2 0.0.0.0:* LISTEN tcp6 0 0 :::111 :::* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 :::60690 :::* LISTEN tcp6 0 0 ::1:25 :::* LISTEN tcp6 0 0 :::2 :::* LISTEN

tak i również na secondary ns2.potel.com.pl

Mam też domenę potel.pl która jest na home.pl i tam też mam ten adres mailowy. Zabieg celowy Klamra domknięta tylko tutaj wkleiłem bez niej . wynik ładowania strery. named-checkzone cyfrowyzasieg.pl /etc/bind/db.cyfrowyzasieg.pl zone cyfrowyzasieg.pl/IN: loaded serial 2016072001 OK Doda też że potel.com.pl też mam wydelegowany na ten sam serwer DNS i tutaj sytuacja jest taka sama z tym, jednocześnie serwer dns od razu korzysta z tej domeny jako ns1.potel.com.pl. Na home.pl podałem nazwe dns1: ns1.potel.com.pl oraz ip strefa dla tej domny wygląda tak: $TTL 3600 $ORIGIN potel.com.pl. @ IN SOA ns1.potel.com.pl. dawid.gras.pl. ( 2016072003 ; Serial 28800 ; Refresh 86400 ; Retry 2419200 ; Expire 86400 ) ; Negative Cache TTL ; @ IN NS ns1.potel.com.pl. @ IN NS ns2.potel.com.pl. @ IN A 91.231.20.206 ns1 IN A 91.231.20.234 ns2 IN A 91.231.20.206 @ IN MX 10 mail.potel.com.pl. mail IN A 91.231.20.206 www IN A 91.231.20.206 ftp IN A 91.231.20.206 named-checkzone potel.com.pl /etc/bind/db.potel.com.pl zone potel.com.pl/IN: loaded serial 2016072003 OK Jakieś pomysły co mogę mieć jeszcze źle?