Piotrus Napisano Marzec 6, 2009 Zgłoszenie Share Napisano Marzec 6, 2009 Witam! Zainstalowalem nowego Bind-a 9.6.0-P1 i zaczęły się pojawiać różne komunikaty w logach. Czy może mi ktoś wytłumaczyć co one oznaczają i ewentualnie jak wyeliminować błędy w konfiguracji? Przypuszczam, że są one związane z rozwiązywaniem adresów przez IPv6. Próbowałem dodać opcję "-4" w pliku /etc/sysconfig/named, aby Bind w pierwszej kolejności rozwiązywał adresy IPv4, ale niewiele to zmieniło. Poniżej fragment moich logów: 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: 1 Time(s) automatic empty zone: 0.IN-ADDR.ARPA: 1 Time(s) 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: 1 Time(s) automatic empty zone: 127.IN-ADDR.ARPA: 1 Time(s) automatic empty zone: 2.0.192.IN-ADDR.ARPA: 1 Time(s) automatic empty zone: 254.169.IN-ADDR.ARPA: 1 Time(s) automatic empty zone: 255.255.255.255.IN-ADDR.ARPA: 1 Time(s) automatic empty zone: 8.E.F.IP6.ARPA: 1 Time(s) automatic empty zone: 9.E.F.IP6.ARPA: 1 Time(s) automatic empty zone: A.E.F.IP6.ARPA: 1 Time(s) automatic empty zone: B.E.F.IP6.ARPA: 1 Time(s) automatic empty zone: D.F.IP6.ARPA: 1 Time(s) client 10.0.0.1 RFC 1918 response from Internet for 1.0.0.10.in-addr.arpa: 1 Time(s) client 10.0.0.27 RFC 1918 response from Internet for 100.0.16.172.in-addr.arpa: 11 Time(s) client 10.0.0.27 RFC 1918 response from Internet for 100.0.168.192.in-addr.arpa: 1 Time(s) client 10.0.0.27 RFC 1918 response from Internet for 101.1.168.192.in-addr.arpa: 41 Time(s) client 127.0.0.1 RFC 1918 response from Internet for 1.0.0.10.in-addr.arpa: 1 Time(s) client 127.0.0.1 RFC 1918 response from Internet for 22.0.0.10.in-addr.arpa: 1 Time(s) client 127.0.0.1 RFC 1918 response from Internet for 27.0.0.10.in-addr.arpa: 2 Time(s) client 127.0.0.1 RFC 1918 response from Internet for 32.0.0.10.in-addr.arpa: 3 Time(s) received control channel command 'stop': 1 Time(s) success resolving '139.128.97.59.in-addr.arpa/PTR' (in '97.59.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving '183.170.198.99.combined.njabl.org/A' (in 'combined.njabl.org'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving '200.132.94.59.in-addr.arpa/PTR' (in '94.59.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving '204.smart-dns.net/A' (in 'smart-dns.NET'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving '23-226-190-89.baltnet.ru/A' (in 'baltnet.ru'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving '240.170.128.85.in-addr.arpa/PTR' (in '170.128.85.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving '34.241.129.62.combined.njabl.org/A' (in 'combined.njabl.org'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving 'a166.d.akamai.net/A' (in 'd.akamai.NET'?) after disabling EDNS: 1 Time(s) success resolving 'atena.nets.pl/A' (in 'nets.pl'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving 'atena.nets.pl/AAAA' (in 'nets.pl'?) after disabling EDNS: 1 Time(s) success resolving 'c303.cloudmark.com/A' (in 'cloudmark.com'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving 'dns.poczta.fm/A' (in 'fm'?) after disabling EDNS: 1 Time(s) success resolving 'images.tuba.fm/A' (in 'tuba.fm'?) after disabling EDNS: 1 Time(s) success resolving 'interia.hit.gemius.pl/A' (in 'gemius.pl'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving 'katowice.biznespolska.pl/A' (in 'biznespolska.pl'?) after disabling EDNS: 1 Time(s) success resolving 'mk.zl.interia.pl/A' (in 'interia.pl'?) after disabling EDNS: 1 Time(s) success resolving 'ns.baltnet.ru/A' (in 'baltnet.ru'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving 'poczta.gazeta.pl/A' (in 'gazeta.pl'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s) success resolving 'poczta.interia.pl/A' (in 'interia.pl'?) after disabling EDNS: 1 Time(s) success resolving 'www.biznespolska.pl/A' (in 'biznespolska.pl'?) after disabling EDNS: 1 Time(s) success resolving 'zone05.adicate.com/A' (in 'adicate.com'?) after disabling EDNS: 1 Time(s) the working directory is not writable: 1 Time(s) using default UDP/IPv4 port range: [1024, 65535]: 1 Time(s) using default UDP/IPv6 port range: [1024, 65535]: 1 Time(s) using up to 4096 sockets: 1 Time(s) Odnośnik do komentarza Udostępnij na innych stronach More sharing options...
Rekomendowane odpowiedzi
Jeśli chcesz dodać odpowiedź, zaloguj się lub zarejestruj nowe konto
Jedynie zarejestrowani użytkownicy mogą komentować zawartość tej strony.
Zarejestruj nowe konto
Załóż nowe konto. To bardzo proste!
Zarejestruj sięZaloguj się
Posiadasz już konto? Zaloguj się poniżej.
Zaloguj się