Re: [RESOLVED] Re: Strange resolver behavior

2008-02-27 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Lambrev wrote: [snip] > Did you check http://tools.ietf.org/html/rfc2782 ? > It is "PROPOSED STANDARD" and MS DNS in Win2003 already uses it (if you > have domain controller for example). If I have understood the RFC correctly, it talks about S

Re: [RESOLVED] Re: Strange resolver behavior

2008-02-27 Thread Stefan Lambrev
Greetings, Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 JINMEI Tatuya / 神明達哉 wrote: [snip] At the beginning I was confused with host(1) and resolver library, they are different problems, sorry for the confusion. I think Hajimu-san's analysis was correct that it was caused by th

[RESOLVED] Re: Strange resolver behavior

2008-02-13 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 JINMEI Tatuya / 神明達哉 wrote: [snip] At the beginning I was confused with host(1) and resolver library, they are different problems, sorry for the confusion. I think Hajimu-san's analysis was correct that it was caused by the check in resolver, here is

Re: Strange resolver behavior

2008-02-13 Thread JINMEI Tatuya / 神明達哉
At Tue, 12 Feb 2008 17:31:57 -0800, Xin LI <[EMAIL PROTECTED]> wrote: > It looks like that certain (mis)configuration by the baidu.com DNS > administrators has caused this, but I have no clue why our resolver > would return NXDOMAIN after it gets a positive response? (Yes, I know > that _ is not

Re: Strange resolver behavior

2008-02-12 Thread Hajimu UMEMOTO
Hi, > On Tue, 12 Feb 2008 21:51:02 -0800 > Xin LI <[EMAIL PROTECTED]> said: delphij> The problem for this is that others (Windows, CentOS) does not enforce delphij> this. Except the RFC violation, is there any other risk having this delphij> compatibility? Yes, I know that the BIND reso

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hajimu UMEMOTO wrote: > Hi, > >> On Tue, 12 Feb 2008 17:31:57 -0800 >> Xin LI <[EMAIL PROTECTED]> said: > > delphij> [EMAIL PROTECTED] ~> host ps_other.a.shifen.com > delphij> ps_other.a.shifen.com has address 202.108.22.46 > delphij> Host ps

Re: Strange resolver behavior

2008-02-12 Thread Hajimu UMEMOTO
Hi, > On Tue, 12 Feb 2008 17:31:57 -0800 > Xin LI <[EMAIL PROTECTED]> said: delphij> [EMAIL PROTECTED] ~> host ps_other.a.shifen.com delphij> ps_other.a.shifen.com has address 202.108.22.46 delphij> Host ps_other.a.shifen.com not found: 3(NXDOMAIN) `_' is not allowed in hostname. Our re

Re: Strange resolver behavior

2008-02-12 Thread Edwin Groothuis
On Tue, Feb 12, 2008 at 07:52:31PM -0800, Xin LI wrote: > Forgot to mention, this happens only with recent FreeBSD versions. With > host(1) from earlier BIND versions there is no problem... I have tried > the same command on an old Linux installation: > > $ host ps_other.a.shifen.com > ps_other.

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Forgot to mention, this happens only with recent FreeBSD versions. With host(1) from earlier BIND versions there is no problem... I have tried the same command on an old Linux installation: $ host ps_other.a.shifen.com ps_other.a.shifen.com has addr

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Xin LI wrote: > Edwin Groothuis wrote: >> On Tue, Feb 12, 2008 at 06:42:37PM -0800, Xin LI wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> Edwin Groothuis wrote: On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: > Re

Re: Strange resolver behavior

2008-02-12 Thread Edwin Groothuis
On Tue, Feb 12, 2008 at 07:09:37PM -0800, Xin LI wrote: > > Yes, but it is the MX record querying it is complaining about. > Well, so perhaps that they are different problems? > > What I think is a problem is that attempting to resolve > 'ps_other.a.shifen.com' gets "Unknown host", here is a quick

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Edwin Groothuis wrote: > On Tue, Feb 12, 2008 at 06:42:37PM -0800, Xin LI wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Edwin Groothuis wrote: >>> On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: Received 127 bytes from 1

Re: Strange resolver behavior

2008-02-12 Thread Edwin Groothuis
On Tue, Feb 12, 2008 at 06:42:37PM -0800, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Edwin Groothuis wrote: > > On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: > >> Received 127 bytes from 127.0.0.1#53 in 0 ms > >> [EMAIL PROTECTED] ~> host ps_other.a.shifen.com >

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Edwin Groothuis wrote: > On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: >> Received 127 bytes from 127.0.0.1#53 in 0 ms >> [EMAIL PROTECTED] ~> host ps_other.a.shifen.com >> ps_other.a.shifen.com has address 202.108.22.46 >> Host ps_other.a.sh

Re: Strange resolver behavior

2008-02-12 Thread Edwin Groothuis
On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: > Received 127 bytes from 127.0.0.1#53 in 0 ms > [EMAIL PROTECTED] ~> host ps_other.a.shifen.com > ps_other.a.shifen.com has address 202.108.22.46 > Host ps_other.a.shifen.com not found: 3(NXDOMAIN) 12:49:45.620015 IP 10.251.1.18.51852 > 202.

Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, It looks like that certain (mis)configuration by the baidu.com DNS administrators has caused this, but I have no clue why our resolver would return NXDOMAIN after it gets a positive response? (Yes, I know that _ is not appropriate for domain name