Hello,
One of our records, s3.xxfy.duowan.com, has been meeting the resolving problem.
The different dns cache will get different result for the resolving.
for example,
$ dig s3.xxfy.duowan.com @202.96.128.166 +short
s3-duowan.xxfy.kunlun.com.
60.28.208.177
$ dig s3.xxfy.duowan.com @8.8.8.8 +sh
On 12/10/10 08:17, Martin McCormick wrote:
As a reminder, none of this is on our master DNS yet so
we are still doing the normal activities. Our firewalls are
supposed to be adjusted to allow the 4096-byte DNS packets in
the next day or so so all the testing is being done on another
box
In article ,
Jorg W Young wrote:
> Hello,
>
> One of our records, s3.xxfy.duowan.com, has been meeting the resolving
> problem.
> The different dns cache will get different result for the resolving.
>
> for example,
>
> $ dig s3.xxfy.duowan.com @202.96.128.166 +short
> s3-duowan.xxfy.kunlun.
"fakessh @" 쓰시길:
> please you have to be in your answer or (...)
Never use "IP6.INT"!
--
소여물 황병희(黃炳熙) | .. 출항 15분전..
"Consult the best lawyers on criminal law."
-- Vito Corleone, "Chapter 20", page 296
pgpx5kH5MbhAQ.pgp
Description: PGP signature
4 matches
Mail list logo