I need help in confirming a simple bind configuration.

At home, beyond a dynamic IP, I run my WEB server on debian lenny. Now I want this computer to be also a DNS server. I have my own domain, I don't care about a secondary server and have no need for a mail server.

Please tell me if my data base configured well. Since my IP is dynamic, I'll run a script and whenever I sense an IP change, I'll stop bind, create new zone files and start it again.

Assuming the IP I receive is 79.180.60.23, is this file is okay.

; example.com
$TTL 604800
@ IN SOA ns1.example.com. root.example.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800); Negative Cache TTL
;
@ IN NS ns1
IN A 79.180.60.23
ns1 IN A 79.180.60.23 ;my case is simple both DNS server and
www IN A 79.180.60.23 ;web server are on the very same debian

how does running a dns server on a dynamic IP help you? If your IP changes, how does anything reach your DNS server to find out??

Don't run your own DNS. User a service like zoneedit.com, and use their scripts to trigger updates when your IP changes

My understanding was that once I start bind, it will the the root server of my domain the IP of my DNS server, based on the following line in the zone file:
ns1 IN A 79.180.60.23

Right.... and when the IP changes...???

This is why, I suggetsed that I'll have a script running, from root, that when it senses an IP change, it will do bind stop, prepare new files, zone and reverse, delete the old ones, and fire again bind.

OK, you're really not getting this.

Firstly rebuilding a zone file is a really bad idea - use dynamic updates instead, but principally, how does anyone EVER use your server in the first place out on the web?

Your understanding of DNS architecturs seems pretty floored. What do you think would happen if you built a zone file for google.com? would 2/3 of the worlds search traffic suddenly hit your machine?

Well I am new to DNS servers, but I want to run my WEB server as well as DNS server on the same computer at home. Presently my WEB site runs on my computer at home and noip does the DDNS, but I am going to buy a domain of my own. Still I want to save and do the DNS server on the very same debian box.

I thought that once I start bind, it will tell the domain company that this is my primary DNS server. When the IP changes, I'll do it again (bind stop, file update, bind start).

What does companies like no-ip do when I notify them on IP change.

I did not understand the example with google, which was mentioned. I'll always point to the domain that I bought.

it will tell the domain company?? how? magic? It'll do no such thing. you need to tell your registrar where your name servers are, and you clearly can't do that if it changes constantly.

You do NOT wnt to run your own name server. not yet. use zoneedit etc, or your registrar may provide their own solution for you already.

So this is to say: that when I buy a domain they' ll ask also for an IP? I have to commit for this IP and can not change it every two weeks on average. Why should the domain company care? It is a matter between my DNS server and their root server only?

Isn't it like I start by storing my site with company A and switch to B?

From a DNS tutorial on this site, I learn that when I register a domain I need also to give names for primary and secondary name servers. When I specify an A record, during the process of configuring bind, I specify IP addresses.

I did not see a restriction on how often one may do it.

Right, step one. you go find a domain registrar that will let you constantly update your NS records. Changing NS records on their stub zone is not at all the same as changing your own A / CNAME records on a whim, and just doesn't happen. Get that sorted first, and THEN worry about the mess you have from continually changing them. from TTL's not being adhered to, from caches containing old data.

Do not run your own DNS server. There is NO benefit to you at all, if it is even possible to achieve what you want in the first place.

If you don't understand the issues that i'm trying to get across to you, that in itself should be enough reason for you to either stop to properly understand the situation or use one of the MANY perfectly good alternatives already available that will put you in a much better solution whatever you manage to end up assembling.