Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Jan 1997 19:14:19 +0100 (MET)
From:      J Wunsch <j@uriah.heep.sax.de>
To:        freebsd-current@FreeBSD.org (FreeBSD-current users)
Cc:        wpaul@skynet.ctr.columbia.edu (Bill Paul), peter@spinner.DIALix.COM (Peter Wemm)
Subject:   Re: Resolver Error 0 (no error)
Message-ID:  <199701021814.TAA08332@uriah.heep.sax.de>
In-Reply-To: <199701021626.LAA10553@skynet.ctr.columbia.edu> from Bill Paul at "Jan 2, 97 11:26:50 am"

next in thread | previous in thread | raw e-mail | index | archive | help
As Bill Paul wrote:

>  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

> Hops 5 through 10 didn't reverse resolve correctly, but:
> 
> [/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

Ah!

It's the slash in the name.  I've also seen this happen for a forward
name resolution in another case, where a target name has an
underscore.  In this case, host(1) did correctly display it, but
telnet to that hostname told me ``Unknown host''.

Standards are a Good Thing, really, but enforcing standards by
annoying users who can't even change the slightest thing on this
(since they aren't the DNS admins of the zones in question) is IMHO
unacceptable.  I vote for reverting our resolver to the traditional
behaviour.  If named spits at boot time about names with an underscore
in a primary or maybe even secondary file, that's fine with me.  I can
either change that myself, or can at least bug the admin of the
primary where i'm a secondary for to do it.  However, if the resolver
library stops resolving these names, it's not okay.

Peter?

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701021814.TAA08332>