Illegal characters question
Ben Frazier
We've got several 4.9.3 and 4.9.4 bind servers that we've allowed the use of
underscores in host names (usually for routers). I know that's not allowed
especially in 8.x, however I compiled and installed 8.1.2 on a server to see
what would happen. I'm seeing messages in my log saying this host
xxx_yyy_zzz.domain.com is invalid - proceeding anyway. BTW, this particular
machine that I'm testing this on is a secondary for our zones. I can still
view those hosts (and reverse) on this particular 8.1.2 server (the primary is
still 4.9.x). Will I loose this kludgey functionalitiy when I upgrade my
primary to 8.1.x? Or will it just continue to spit out errors and let me go
on my merry way resolving?
Thanks.
--
Ben Frazier
ran...@nospam.chariott.com
"There are two major products that come out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence." - Jeremy S. Anderson
Thorin D. Miley
[Posted and mailed]
In article <MPG.fdf2be6a...@news.compaq.com>,
ran...@nospam.chariott.com (Ben Frazier) writes:
>
> We've got several 4.9.3 and 4.9.4 bind servers that we've allowed the use of
> underscores in host names (usually for routers). I know that's not allowed
> especially in 8.x, however I compiled and installed 8.1.2 on a server to see
> what would happen. I'm seeing messages in my log saying this host
> xxx_yyy_zzz.domain.com is invalid - proceeding anyway. BTW, this particular
> machine that I'm testing this on is a secondary for our zones. I can still
> view those hosts (and reverse) on this particular 8.1.2 server (the primary is
> still 4.9.x). Will I loose this kludgey functionalitiy when I upgrade my
> primary to 8.1.x? Or will it just continue to spit out errors and let me go
> on my merry way resolving?
>
> Thanks.
As far as I can tell it will let you keep resolving. I run all 8.1.2 servers at the moment and one of the clients we do secondary for has a Novell network that includes many underscored names. BIND 8.1.2 seems to spit out the error message and proceed.
>
Cricket Liu
>We've got several 4.9.3 and 4.9.4 bind servers that we've allowed the use of
>underscores in host names (usually for routers). I know that's not allowed
>especially in 8.x, however I compiled and installed 8.1.2 on a server to see
>what would happen. I'm seeing messages in my log saying this host
>xxx_yyy_zzz.domain.com is invalid - proceeding anyway. BTW, this particular
>machine that I'm testing this on is a secondary for our zones. I can still
>view those hosts (and reverse) on this particular 8.1.2 server (the primary is
>still 4.9.x). Will I loose this kludgey functionalitiy when I upgrade my
>primary to 8.1.x? Or will it just continue to spit out errors and let me go
>on my merry way resolving?
BIND 8 has configurable name checking, just like BIND 4.9. In BIND 8,
you use the check-names substatement in a zone or an options
statement.
Barry Margolin
In article <MPG.fdf2be6a...@news.compaq.com>,
Ben Frazier <ran...@nospam.chariott.com> wrote:
>
>We've got several 4.9.3 and 4.9.4 bind servers that we've allowed the use of
>underscores in host names (usually for routers). I know that's not allowed
>especially in 8.x, however I compiled and installed 8.1.2 on a server to see
>what would happen. I'm seeing messages in my log saying this host
>xxx_yyy_zzz.domain.com is invalid - proceeding anyway. BTW, this particular
>machine that I'm testing this on is a secondary for our zones. I can still
>view those hosts (and reverse) on this particular 8.1.2 server (the primary is
>still 4.9.x). Will I loose this kludgey functionalitiy when I upgrade my
>primary to 8.1.x? Or will it just continue to spit out errors and let me go
>on my merry way resolving?
The defaults in BIND 4.9.5 and beyond are to warn about invalid names in a
secondary zone, and reject them in a primary zone.
In BIND 8 you can use the "check-names master warn" or "check-names master
ignore" options to prevent it from rejecting zones that have hostnames with
invalid characters in them.
--
Barry Margolin, bar...@bbnplanet.com
GTE Internetworking, Powered by BBN, Cambridge, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Jim Reid
ran...@nospam.chariott.com (Ben Frazier) writes:
> We've got several 4.9.3 and 4.9.4 bind servers that we've allowed the use of
> underscores in host names (usually for routers). I know that's not allowed
> especially in 8.x, however I compiled and installed 8.1.2 on a server to see
> what would happen. I'm seeing messages in my log saying this host
> xxx_yyy_zzz.domain.com is invalid - proceeding anyway. BTW, this particular
> machine that I'm testing this on is a secondary for our zones. I can still
> view those hosts (and reverse) on this particular 8.1.2 server (the primary is
> still 4.9.x). Will I loose this kludgey functionalitiy when I upgrade my
> primary to 8.1.x? Or will it just continue to spit out errors and let me go
> on my merry way resolving?
You can use the check-names directive in the named.conf file - on a
per zone basis if need be - to allow illegal names to be ignored,
tolerated or rejected. In BIND4.9 this can also be done on a global
basis for all the zones that are listed as primary or secondary
(master and slave in today's jargon) in named.boot. Consult the
documentation: the html directory in BIND8 or the man directory in
BIND4.