Hi Pete
What you are suggesting may solve my problem for me. I just don't
understand how to do what you are suggesting.
The information you are looking for is the following
The DNS sever is running the default Bind (named daemon) on Redhat 6.2.
DNS servers is running just for internal use only with domain zone for all
of the private address space.
There a number of servers, mostly windows NT4 with uderscore in there
names. There are databases and application referencing these machines by
name.
We are working at changing the server names, but some just can't be done
quickly and this leading to other problems.
If I have left anything out please ask.
david
On Thu, 12 Apr 2001, Pete Peterson wrote:
>
> It would help if you explained the situation a bit further.
>
> Are you running a nameserver for some zone on one or more of these
> Linux machines?
>
> Are the other machines, Linux, Solaris, Other-Unix, Windoze, ...?
>
> Are you running NIS in your environment so and distributing hosts files as
> well as DNS records?
>
> When I first encountered this problem it was in a mixed NIS/DNS environment
> where the NIS master hosts file was the primary source of host name vs.
> IP info. To get around the immediate problem when installing a new BIND to
> replace ancient versions, I wrote a trivial script to modify the hosts
> file, preceding any name containing underscores with the same name, but
> with the underscores changed to hyphens.
> ---
> 132.223.240.99 blue-stalactite blue_stalactite # system in Carlsbad Caverns
> ---
> NIS understands both names, so any NIS clients were happy. I use h2n to
> generate the zone file for that zone from the hosts file. It puts in
> the hyphened name as an A-record and the underscored name as a CNAME.
> BIND has no problem with CNAMEs containing underscores, so everthing worked
> fine. You can call it a kludge, but it gave us time to get rid of
> references to the underscored names and eliminate them from the hosts file
> and hence from the zone files.
>
> pete peterson
>
>
>
> > Date: Wed, 11 Apr 2001 16:34:21 -0400 (EDT)
> > From: David Brett <[EMAIL PROTECTED]>
> > To: Vidiot <[EMAIL PROTECTED]>
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: DNS names with "_"
> > Reply-To: [EMAIL PROTECTED]
> >
> > I realize the question was worded poorly. Is it possible to have named
> > look at the host file first and use your idea of an alias for the bad
> > hostname?
> >
> > If not the host file on all computers may work. I may be able to script
> > this. I will not be publishing these bad hostnames to the public network
> > just internal. So any way which will have named give the correct response
> > is acceptable in this case.
> >
> >
> > david
> >
> > On Wed, 11 Apr 2001, Vidiot wrote:
> >
> > > david posted:
> > >
> > > >Does anybody know of a way to allow DNS names with "_" in them? I have a
> > > >number of servers with an underscore in them. It is going to take a lot
> > > >of work to make the change by a large number people.
> > >
> > > Check RFC-1034 and RFC-1035 for details, but I believe it is illegal to
> > > have underscores in a hostname. BTW, it is hostname, not DNS names.
> > > This means you have to change all of your hostnames to legal names
> > > if you want named to work.
> > >
> > > But, you can do the following to each machine:
> > >
> > > /etc/hosts:
> > >
> > > 123.456.789.012 bad_hostname bad-hostname
> > >
> > > By adding an alias to the hosts file, you can now have the named entries
> > > point to the good bad-hostname. It still means editing all of the hosts
> > > files on all of the machines. Without doing doing that, you will not be able
> > > DNS any of the machines. By adding the alias, anything that you have that
> > > references the bad name will still work. BUT, if you rely upon named to
> > > resolve it for you... nope, ain't gonna happen.
> > >
> > > The above information is my understanding of the situation.
> >
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
