Re: DNSy dla *.neostrada.pl

Krzysztof Halasa <khc@pm.waw.pl> napisal(a) w wiadomosci
news:m3skt5zre8.fsf@maximus.localdomain...
> To z pewnoscia nie jest problem polskiego Internetu, ale:
> $ host -v news.neostrada.pl. ns1.hosting.tp.pl.
> Trying "news.neostrada.pl"
> ;; connection timed out; no servers could be reached
>
> $ host -v news.neostrada.pl. ns2.hosting.tp.pl.
> Trying "news.neostrada.pl"
> ;; connection timed out; no servers could be reached
Teraz oba serwery odpowiadaja:

C:\Documents and Settings\Marek>host -v news.neostrada.pl.
ns1.hosting.tp.pl.
Trying "news.neostrada.pl"
Using domain server:
Name: ns1.hosting.tp.pl.
Address: 193.110.120.122#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 879
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;news.neostrada.pl. IN A

;; ANSWER SECTION:
news.neostrada.pl. 3600 IN A 193.110.122.97

;; AUTHORITY SECTION:
news.neostrada.pl. 3600 IN NS ns2.hosting.tp.pl.
news.neostrada.pl. 3600 IN NS ns1.hosting.tp.pl.

Received 98 bytes from 193.110.120.122#53 in 78 ms
Trying "news.neostrada.pl"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1943
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;news.neostrada.pl. IN AAAA

Received 35 bytes from 193.110.120.122#53 in 78 ms
Trying "news.neostrada.pl"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1500
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;news.neostrada.pl. IN MX

;; ANSWER SECTION:
news.neostrada.pl. 3600 IN MX 5 mail.hosting.tp.pl.

;; AUTHORITY SECTION:
news.neostrada.pl. 3600 IN NS ns2.hosting.tp.pl.
news.neostrada.pl. 3600 IN NS ns1.hosting.tp.pl.

Received 103 bytes from 193.110.120.122#53 in 78 ms

C:\Documents and Settings\Marek>host -v news.neostrada.pl.
ns2.hosting.tp.pl.
Trying "news.neostrada.pl"
Using domain server:
Name: ns2.hosting.tp.pl.
Address: 193.110.120.125#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 563
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;news.neostrada.pl. IN A

;; ANSWER SECTION:
news.neostrada.pl. 3600 IN A 193.110.122.97

;; AUTHORITY SECTION:
news.neostrada.pl. 3600 IN NS ns2.hosting.tp.pl.
news.neostrada.pl. 3600 IN NS ns1.hosting.tp.pl.

Received 98 bytes from 193.110.120.125#53 in 78 ms
Trying "news.neostrada.pl"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1137
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;news.neostrada.pl. IN AAAA

Received 35 bytes from 193.110.120.125#53 in 78 ms
Trying "news.neostrada.pl"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 129
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;news.neostrada.pl. IN MX

;; ANSWER SECTION:
news.neostrada.pl. 3600 IN MX 5 mail.hosting.tp.pl.

;; AUTHORITY SECTION:
news.neostrada.pl. 3600 IN NS ns2.hosting.tp.pl.
news.neostrada.pl. 3600 IN NS ns1.hosting.tp.pl.

Received 103 bytes from 193.110.120.125#53 in 78 ms

-- 
Mark
keitaro@pnet.pl
keiichi@onet.pl