BIND 8.2 Problems ...

[Barry Margolin]

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.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.