I want to buy a domain name from, let's say, godaddy.com and set up my own bind servers, master and slave, and make them authoritative for the domain, let's say, example.com. Let's also say, my machines are 323.453.567.786 and 323.453.567.787 (please don't mind the impossible, imaginary example numbers). The question is, if thees machines have no other names associated with them, do i just give godaddy thees two IP addresses, they organize, that NS records for example.com get added against thees IP-s and i myself manage further A records for my DNS servers, like ns1.example.com and ns2.example.com.

Hope you understand my question.. this far i have used my isp's DNS servers and gave godaddy information like ns1.myisp.com and ns2.myisp.com.

basically, yes. any new dns queries come up for the root servers, through godaddy's registry and along to you. you then give out your own MX details etc...

if this is only a small setup, and you've not done dns before, i'd personally advise against it. instead, mayeba service like zoneedit.com will suffice your DNS needs. you're in total control of any domain you buy, and it's free, but you won't get bit in the bum if your IP changes etc...

Well, i plan to move some 10 sites from hosting company to my own server (since we built LTSP and therefore have server room and all the necessary stuff, including some backup servers with no particular load) and further on house some of our client's virtual servers. So i need to set up my dns servers anyway. I have done DNS before too and experimented with the technical part of it in my LAN, so this wouldn't be a problem i think.

About the IP changes, in this case (but that is very unlikely to happen) i imagine it is possible to acknowledge godaddy about this and they will edit the NS records?

if you don't specifically pay for a static IP, then you must guard against the potential of it changing. You seem to be in a suitable position to do it yourself after all, but you might like to look at using zoneedit as a secondary DNS server or such like. this way you could serve all main requests yourself, but if it were to change, you could dynamically update zoneedit's details and have minimal service downtime until you manually sort yourself out. This sort of functionality is not normally provided by an registrar like godaddy, it's just not their job, and requesting them to update DNS addresses is typically a manual process with a couple of days turnaround. that's not good for you. of course, you might rather upgrade to a static IP if you aren't already. it's simpler, but would naturally cost a little more.

Yes, of course i have static IP (5 of them indeed ). My ISP is also willing to act as slave DNS to my zone(s). An unlikely chance of the IP change exists, as this is not exactly the most stable (i mean economically) ISP around, can't predict if its closed down tomorrow or not.

well, now i've been told, that i can't use IP-s to register my nameservers. i must have a valid hostname and reverse provided by my ISP and then i give hostname to registrar, like ip-1-2-3-4.my-isp.com. luckily my isp is willing to give me special names, like mycompany1.my-isp.com and mycompany2.my-isp.com, so that even if my ip changes after some years (isp doing some rearrangements in it's network etc.) i still have these names and nameservers continue to work. have i got it correct?