Skip site navigation (1)Skip section navigation (2)
Date:      2 Jan 1997 20:54:17 GMT
From:      peter@spinner.DIALix.COM (Peter Wemm)
To:        freebsd-current@freebsd.org
Subject:   Re: Resolver Error 0 (no error)
Message-ID:  <5ah79p$8rh$3@haywire.DIALix.COM>
References:  <199701020846.JAA03861@uriah.heep.sax.de>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <199701021626.LAA10553@skynet.ctr.columbia.edu>,
	wpaul@skynet.ctr.columbia.edu (Bill Paul) writes:
> This reminds me:
> 
> [/homes/wpaul]:marple{15}% traceroute freebsd.org
> traceroute to freebsd.org (204.216.27.18), 30 hops max, 40 byte packets
>  1  ctr-gw.ctr.columbia.edu (128.59.74.1)  2.741 ms  2.465 ms  2.467 ms
>  2  mudd-gw.net.columbia.edu (128.59.62.1)  4.353 ms  3.124 ms  3.038 ms
>  3  128.59.45.2 (128.59.45.2)  45.279 ms  49.961 ms  51.045 ms
>  4  nyser-gw.net.columbia.edu (128.59.247.1)  189.497 ms  112.663 ms  100.243 ms
>  5  169.130.12.5 (169.130.12.5)  91.750 ms  98.124 ms  102.126 ms
>  6  169.130.1.101 (169.130.1.101)  82.285 ms  74.644 ms  79.732 ms
>  7  144.228.60.1 (144.228.60.1)  281.282 ms  141.881 ms  219.776 ms
>  8  198.67.2.11 (198.67.2.11)  118.587 ms  110.496 ms  113.735 ms
>  9  144.228.10.102 (144.228.10.102)  259.932 ms  149.262 ms  149.992 ms
> 10  144.228.10.50 (144.228.10.50)  231.764 ms  217.007 ms  238.777 ms
> 11  pb-nap.crl.net (198.32.128.20)  147.369 ms  156.685 ms  149.741 ms
> 12  E0-CRL-SFO-02-E0X0.US.CRL.NET (165.113.55.2)  166.600 ms  183.481 ms  253.803 ms
> 13  T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)  131.645 ms  135.416 ms  163.520 ms
> 14  freefall.FreeBSD.ORG (204.216.27.18)  160.483 ms *  312.308 ms
> [/homes/wpaul]:marple{16}% uname -sr
> FreeBSD 2.2-BETA_A
> 
> Hops 5 through 10 didn't reverse resolve correctly, but:

Actually they did.. :-]  They resolved to illegal unpresentable data..
 
> [/homes/wpaul]:marple{17}% nslookup 169.130.12.5
> Server:  sirius.ctr.columbia.edu
> Address:  128.59.64.60
> 
> Name:    ny-nyc-2-H4/0-T3.nysernet.net
> Address:  169.130.12.5
> 
> With FreeBSD 2.1.0:
> 
> [/home/wpaul]:OmniVAX{36}% traceroute freebsd.org
> traceroute to freebsd.org (204.216.27.18), 30 hops max, 40 byte packets
>  1  ctr-gw.ctr.columbia.edu (128.59.64.1)  169.288 ms  226.311 ms  197.468 ms
>  2  mudd-gw.net.columbia.edu (128.59.62.1)  175.367 ms  227.903 ms  347.029 ms
>  3  128.59.45.2 (128.59.45.2)  222.734 ms  233.502 ms  218.619 ms
>  4  nyser-gw.net.columbia.edu (128.59.247.1)  208.978 ms  309.440 ms  224.325 ms
>  5  ny-nyc-2-H4/0-T3.nysernet.net (169.130.12.5)  298.337 ms  271.123 ms  266.279 ms
>  6  ny-pen-1-H2/0-T3.nysernet.net (169.130.1.101)  363.654 ms  297.084 ms  362.543 ms
>  7  sl-pen-1-F0/0.sprintlink.net (144.228.60.1)  295.228 ms  426.730 ms  339.896 ms
>  8  sl-pen-11-F/T.sprintlink.net (198.67.2.11)  239.456 ms  283.974 ms  248.982 ms
>  9  sl-stk-1-H12/0-T3.sprintlink.net (144.228.10.102)  448.619 ms  335.131 ms *
> 10  * * sl-stk-nap-H2/0-T3.sprintlink.net (144.228.10.50)  433.355 ms
> 11  pb-nap.crl.net (198.32.128.20)  371.726 ms  397.078 ms  362.136 ms
> 12  E0-CRL-SFO-02-E0X0.US.CRL.NET (165.113.55.2)  373.627 ms  464.830 ms  397.843 ms
> 13  T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)  398.602 ms  393.075 ms  479.812 ms
> 14  freefall.FreeBSD.ORG (204.216.27.18)  343.168 ms  467.463 ms  371.996 ms

And check to see what freebsd-2.1.0 does when getting a PTR record containing
an '&', '|' or ';' character and consider the implications for hostnames
being passed to commands from gethostbyaddr() via system().

> Granted this is Sprint we're talking about here, but this seems a little
> odd. My named is from BIND 4.9.5-REL.
> 
> -Bill

The version of named you are running would complain bitterly if it you tried
to do a zone transfer of the sprintlink reverse mapping tables.

The Authors of BIND didn't make the decision to make this change lightly..
Bind's resolver is now inline with other vendors.

Fortunately, DNS corruption seems to be forcing the old named's out of
business, so it will not be long before the last of these illegal names
are gone.  (Incidently, it's the checks in the recent bind's that make it
more resistant to corruption that are causing the timeouts Joerg is seeing).

-Peter



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5ah79p$8rh$3>