BUG ON BIND 4.9.2?

Hello there.
I'm Nicola Roserba and I work on Interbusiness, Italy.

I wish to let you know that I've probably found a bug on the Bind 4.9.2.

If you define new machines on a zone in this way:

machine.domain.something	IN	A	194.243.100.001
anothermachine.domain.something	IN	A	194.243.100.002

and then you query that zone, in this way:

host -avl domain.something authoritative-DNS-for-that-domain

you'll probably receive this:

machine.domain.something	IN	A	194.243.100.wrong-IP
anothermachine.domain.something	IN	A	194.243.100.wrong-IP.

"wrong-IP" means that you will receive a different last byte in IP address
for example:

machine.domain.something	IN	A	194.243.100.4


If you remove the zeroes in the last byte of the zone where you define
the machine, like this:

machine.domain.something	IN	A	194.243.100.1
anothermachine.domain.something	IN	A	194.243.100.2


the DNS will amswer correctly.

So it seems like the BIND doesn't appreciate the zeroes in a IP address 
definition.

I can't find errors in my BIND configuration so I think this is a bug.
Do you agree?

Bye


_____________________________________________________________________________
         ,=======>-------.              
 ,-------|------.        |   Centro Gestione            
 |       `------|--------'    INTERBUSINESS     ING. NICOLA ROSERBA 
 `-------<======'
__________________________/\_______________     Phone: +39-6-36889293
__________________________/\___                 Fax:   +39-6-33659922
__________________________/\___T E L E C O M    roserba at cgi.interbusiness.it
__________________________/\__________Italia_________________________________