Re: DNSy dla *.neostrada.pl - Grupy dyskusyjne w eGospodarka.pl

eGospodarka.pl › Grupy › pl.internet.polip › DNSy dla *.neostrada.pl › Re: DNSy dla *.neostrada.pl

From: "Mark" <t...@p...pl>
Newsgroups: pl.internet.polip
References: <m...@m...localdomain>
Subject: Re: DNSy dla *.neostrada.pl
Date: Sat, 16 Aug 2008 18:32:37 +0200
Lines: 109
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: 83.28.109.34
Message-ID: <48a70125$1@news.home.net.pl>
X-Trace: news.home.net.pl 1218904357 83.28.109.34 (16 Aug 2008 18:32:37 +0200)
Organization: home.pl news server
X-Authenticated-User: tenchi.hot
Path: news-archive.icm.edu.pl!newsfeed.gazeta.pl!news.home.net.pl!not-for-mail
Xref: news-archive.icm.edu.pl pl.internet.polip:86901
[ ukryj nagłówki ]
Krzysztof Halasa <k...@p...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
k...@p...pl
k...@o...pl