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@cgi.interbusiness.it __________________________/\__________Italia_________________________________
machine.domain.something IN A 194.243.100.001 anothermachine.domain.something IN A 194.243.100.002
"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
So it seems like the BIND doesn't appreciate the zeroes in a IP address definition.
This is not a bug. Bind considers leading zeros be represent octal information. Therefore, 002 != 2. Not a bug. A feature. Not all numbers are decimal. -- --bill
This is not a bug. Bind considers leading zeros be represent octal information. Therefore, 002 != 2. Not a bug. A feature. Not all numbers are decimal. True, but what's the difference between octal 002 and decimal 2 (and if you like, hexadecimal 0x2)? Piet
This is not a bug. Bind considers leading zeros be represent octal information. Therefore, 002 != 2. Not a bug. A feature. Not all numbers are decimal. True, but what's the difference between octal 002 and decimal 2 (and if you like, hexadecimal 0x2)?
Piet
I guess it depends on your calculator. 2 != 02 != 002 on my desktop TI. -- --bill
In message <9606101513.AA01132@cgi.interbusiness.it.interbusiness.it> you write :
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?
Using 001 and 002 was not a good example to choose ;-) This is more of a feature than a bug. Bind (like many other programs) uses the convention that octal numbers start with a leading "0" and hexadecimal numbers start with a leading "0x" to allow you to write things like localhost IN A 0x7f.000.000.1 in your zone files should you so wish. James ======= ___ === James Aldridge, Network Engineer, ====== / / / ___ ____ _/_ ==== EUnet Communications Services BV ===== /--- / / / / /___/ / ===== Singel 540, 1017 AZ Amsterdam, NL ==== /___ /___/ / / /___ /_ ====== Tel. +31 20 6233803; Fax. +31 20 6224657 === ======= [ 24hr emergency number +31 20 4210865 ]
participants (4)
-
bmanning@ISI.EDU
-
James Aldridge
-
Nicola Roserba
-
Piet Beertema