Please remember to reply to the mailing list, not the original sender: http://gnudip2.sourceforge.net/#mailinglist
+++++++++ > > my first impression is, that it can't be that dificult... > > but that is, how it usually goes, right? > > Right. Let me know if I can help. alright, here it comes :-) i don't think i understood the concept behind the backend server stuff quite yet. i have entry: nsupdate = /usr/local/gnudip/sbin/gdipckclt.pl tinydns in my gnudip.conf this means that all updates shoul go over the tinydns backend, correct? in the backend.conf i have the following: fifo.tinydns = /usr/local/gnudip/run/tinydns and reload.tinydns = /usr/local/gnudip/sbin/gdiprltiny.sh <somedomain> and then i also have the backendserver running /usr/local/gnudip/sbin/gdipbksrv.pl /usr/local/gnudip/run/tinydns i have no clue, whether any of this is working, and this is not yet my question. i'd like to know how data is passed between all these parts. ie. what happens, when a user updates his ip using a gnudip compatible client. what data is passed through the fifo? my guess, so far, is that gdipbkclt.pl is sending data through the fifo to the gdipbksrv.pl which in turn is acting as specified in backend.conf. (do i need to restart gdipbksrv.pl when i change backend.conf?) what data? gdipbksrv.pl runs in my case gdiprltiny.sh... what is the <somedomain> argument for? if i understand it correctly i would need one line per domain then? i see how this would be necessary when using bind, but tinydns can work with one datafile only.... is this somehow possible? am i way off? thanks greetings Thilo -- GnuDIP Mailing List http://gnudip2.sourceforge.net/#mailinglist
