The first time the steering wheel manually DNS'kami, and immediately had problems. Even friends who did not just say that strange problem.
We have Debian Stable on VDS (firstvds unfortunately) and bind (8.4.7). It turns a couple of PHP saytik, customer server (but you can do anything). And have your cool server with Debian Squeeze, which raised a website in Python (just the VDS smallest, not mastered it Python from memory). To the IP of the VDS tied to the main domain, call it domain.ru. You may want one of the subdomains addressed in my IP. That is domain.ru — on the IP VDS, sub.domain.ru — in my. The task seems to be simple, but then the fun begins.
The zone file:
$TTL 3600
domain.ru. IN SOA ns1.firstvds.ru. root.domain.ru. (2010090201 10800 3600 604800 86400)
domain.ru. IN NS ns1.firstvds.ru.
domain.ru. IN NS ns2.firstvds.ru.
domain.ru. IN NS ns3.firstvds.ru.
domain.ru. IN MX 10 mail
domain.ru. IN MX 20 mail
domain.ru. IN A [IP VDS]
www IN A [IP VDS]
ftp IN A [IP VDS]
mail IN A [IP VDS]
smtp IN A [IP VDS]
pop IN A [IP VDS]
sub IN A [IP of your server] # - all the fun here
All up, the zone ID in the first line is also constantly changing as expected. bind is restarted after a few hours, DNS was updated and if over SSH from VDS to do:
root:~# host sub.domain.ru
sub.domain.ru A [IP of my server]
And, it would seem that everything is fine. Only here every 3-4 hours (when updated DNS's) he changes IP. The subdomain has the old IP. That's how it looks with my car (the console just shows it is possible to trace):
[21:24:05]:[email protected] ~>nslookup sub.domain.ru
Server: 192.168.0.1
Address: 192.168.0.1#53
Non-authoritative answer:
Name: sub.domain.ru
Address: [new IP]
[23:26:06]:[email protected] ~>nslookup sub.domain.ru
Server: 192.168.0.1
Address: 192.168.0.1#53
Non-authoritative answer:
Name: sub.domain.ru
Address: [old IP, which is VDS]
So you can see what DNS here and there jumping. After a few hours becomes normal again, then again old. Website launching soon, so I would like to get rid of this. And I myself do it the first time, so as not TRU admin. Even tried using control panel to remove the domain and add it again. Same crap, but it happens and both IP Non-authoritative answer come.
This has been occurring for more than a month. I changed the zone file repeatedly. In support FirstVDS to go I don't even know whether, as they always say "your server — your problem" and advise all to be reinstalled.
P. S.: at Once I apologize for a made-up domains, I hope it is clear explained.