I have a shiny new 2003 server that is frustrating me. I have configured my BIND server to accept information from my AD server but when I force the AD server to transfer information the AD server sends the infor to the loopback address instead of the Primary DNS (My BIND server). I have set the IP for my BIND server in the NIC settings under "Preferred DNS server".

When checking the logs I see a DnsApi error. Relevant info below:
DNS server list:
192.168.0.10
Sent update to server: 127.0.0.1
IP Address(es):
192.168.0.5

To me it is saying "i was told to register with dns server x but i decided i would use dns server q for no apparent reason"- not that servers really talk but anyway. :)

Anyone have any thoughts?

Specify the IP address of your Linux box on the zone transfers tab of your DNS zone on your 2003 machine, also check that bind secondaries are allowed (should be by default) and that your zone type is primary and not AD integrated. I would use the 2003 Server as a primary DNS and the BIND as secondary if I were you. 2003 DNS supports dynamic DNS so your clients or DHCP will update the DNS zone which would then be replicated to the BIND Deamon for fault tolerance.