I tried to change option broadcast-address to 192.168.0.255, but i get the same error in syslog.... also now I cant get IP from the DHCP server

Can you post the output of ifconfig? Are you able to ping, or otherwise communicate with, hosts on your LAN (this may require setting up a temporary static IP on a LAN host in the subnet 192.168.0.0/24).
It is curious that changing an option setting affects your ability to acquire an IP. Or am I misunderstanding what you mean by 'I cant get IP from the DHCP server'? In cases like this, it is helpful to be very clear about what DHCP server & client is being described. Your 'netserver' is both a DHCP server and client. The rest of the DHCP clients will be on your LAN, and the other DHCP server of interest is on the WAN/ISP side of the router (netserver).
To proceed, I think we need to establish that the LAN side ethernet interface is up and has valid networking parameters associated with it.
I agree that the broadcast-address option should be as gezley describes. I also wonder whether you really want 'option domain-name-servers 192.168.0.100;'. This would tell your LAN clients that your router is their nameserver, and I assume you don't have that set up (at least not yet, and I don't imagine you'd want to). It is probably a good idea to look in /etc/resolv.conf, and see what your ISP says should be used as a nameserver(s). Put this in the domain-name-server option.

--- rod.

I got it!

I feel pretty stupid right now... Ive found the problem. I completely forgot to specify the IP of eth1 in the inet1.conf file... thats why dhcpd was complaining about no IP to deal with... now everything is working perfectly, I can access the web from all the clients on the lan side.

Thanks to all who helped me!

Whoops, not this thread.