You seem to be confused about what does what in a networked enviornment. First and foremost, BIND is the mother of all DNS systems. It is easily the best, but it is just that, DNS. It isn't intended to be part of an Active Directory system, as AD is a zoo of closed source, and a waste of time. There are tons of postings on the web about using BIND with AD, and there is no need to rehash that here. If you really want to do this (and incase you haven't noticed it yet, I strongly suggest you don't), you need to get a functioning version of SAMBA server running on the BIND box, making the linux box into the domain controller. If you need a domain (waste of time and resources to me, but its your money and time), I suggest using the BIND boxes for straight DNS work (resolving the internet addresses, nothing more), and leave the AD to the M$ domain controller.
Adding IP addresses to named.conf won't work in any way. You have it backwards. You don't add IP addresses, you add domain names to named.conf, the only IP addresses would be for PTR lookups, and chances are very good that you aren't authoritative for any real world IP space, so you don't have to create PTR records. You could add the domain adsucks.com to your named.conf, then create a zone file called adsucks.com, and in it put the IP address of your winblows host. Then any machine using your BIND box for DNS can lookup adsucks.com, and get the IP of the box. If you want to use DNS, I strongly suggest getting the book DNS and BIND from O'Reilley. It spells everything out nicely.