H2N does not allow some hostnames

Waltner, Steve swaltner at lsil.com
Wed Jan 3 20:12:54 UTC 2001


Two things, grab h2n from
ftp://ftp.uu.net/published/oreilly/nutshell/dnsbind/dns.tar.Z. I did this
earlier today, and it was able to generate an A record for a host called
in-ste-ch-bsl-r-01-atm2-0 in a test hosts file that I had, so h2n should
work properly with this hostname. The other idea is that this host might be
in a different network than you specified by the -n argument to h2n. If this
is the case, the entry will not be migrated to the zone file. In other words
a hosts file with

172.16.0.1	server1
172.17.0.1	server2

and running "h2n -d foo.com -n 172.16" will only put the server1 entry into
your db.foo.com file. If that's not the case, post a portion of your
/etc/hosts file including entries that get converted properly as well as
some of the addresses that don't get converted as well as the syntax you are
using on h2n. With the information you have given the group, there isn't
anything obvious that is broken with those hostnames and I can get it to
convert using the h2n included in the archive listed above.

--
Steve Waltner
LSI Logic
Steve.Waltner at lsil.com

> ----------
> From: 	Stefan Schweizer
> Sent: 	Wednesday, January 3, 2001 11:07 AM
> To: 	comp-protocols-dns-bind at moderators.isc.org
> Subject: 	Re: H2N does not allow some hostnames
> 
> 
> Hi Jim
> 
> Thanks for your answer.
> 
> Jim Reid wrote:
> 
> > >>>>> "Stefan" == Stefan Schweizer <sschweizer1 at hotmail.com> writes:
> >
> >     Stefan> I have the problem that we have hostnames like
> >     Stefan> in-ste-ch-bsl-r-01-atm2-0.
> >
> > Nice!
> >
> 
> Yeh ;-)
> 
> >
> > It might be better to give your hosts names that are easy to pronounce
> > and remember. Higher-level components of the domain name could be used
> > to encode information like location, organisational unit and the type
> > of device that the hosts belongs too. eg:
> >         atm0.router.sales.geneva.example.com
> >
> 
> You have right, but the naming convention is always a strange thing.
> 
> >
> >     Stefan> We have this in a database and
> >     Stefan> make an hostfile style extract and h2n convert this in to
> >     Stefan> a zonefile. This works fine but with the hostname above it
> >     Stefan> doesn't work. I found some infos that it's allowed to use
> >     Stefan> - (hyphens?) between characters. Has someone a Idea what
> >     Stefan> the problem can be?
> >
> > The example name you gave is legal, so there's no reason for the name
> > server to reject it. Underscores are not allowed in hostnames, though
> > RFC2181 says name servers should not "refuse to serve a zone because
> > it contains labels that might not be acceptable to some DNS client
> > programs". If the name server is objecting, it's a bug. By default
> > BIND8 rejects zones containing hostnames with illegal characters. This
> > should be considered a feature rather than a bug. :-) If the name
> > isn't in the file h2n generates or if h2n is complaining, then it's a
> > bug in h2n.
> 
> Thanks for this explanation. I think also that its h2n who who doesn't
> convert this name in to the zone. But my problem is that i can't find the
> code in h2n which looks if there is any not allowed character in the
> hostnames used.
> 
> May be you have a hint
> 
> Thanks
> 
> Stefan
> 
> 
> 
> 
> 




More information about the bind-users mailing list