BIND 8.2 Problems ...

[Mark_Andrews at isc.org]

> In article <7rj3js$1mp$1 at goo.nwd.usace.army.mil>,
> Carl Hilton <chilton at sac.usace.army.mil> wrote:
> >My system was working and it stopped.... Now the question is why.....
> >
> >My folks have the need to have Domain Lookups on some specific machines
> >without using FQDN (ie... mymachine1 and have this resolve to
> >XXX.XXX.XXX.XXX).
> >
> >I currently have in my bind file...
> >
> >$ORIGIN .
> >
> >mymachine1  IN CNAME mymachine1.mydomain.com.
> >
> >
> >$ORIGIN mydomain.com
> >
> >mymachine1   A aaa.bbb.ccc.ddd
> >
> >
> >
> >
> >Is this not the correct approach? Like I said this was working last week but
> >now it's not... The only thing that changed was that the actual machine
> >"mymachine" which is an NT SERVER was changed out.... the current machine
> >does have the correct IP address and I can ping it by IP or by FQDN.
> 
> Did you upgrade BIND in the process?  Ever since BIND 4.9.x, BIND has not
> allowed you to have names in a zone file that are not in the zone assigned
> to that file.  If the above lines are in the zone file for mydomain.com,
> the CNAME record will be rejected because it's outside the zone.
> 
	Also the correct way to achieve this is to set search lists
	on the client machines.  All OS's have ways to do this.
	For UNIX boxes it is set in resolv.conf.  For Windows boxes
	this is set through the Network control panel.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org