For the first time manually steer DNS'kimi, and immediately had a problem. Even friends who have done this often say strange problems.
We have: Debian Stable on VDS (firstvds, unfortunately) and bind (8.4.7). It runs a pair of PHP-sites, the customer's server (but you can do anything). And we have our own cool server with Debian Squeeze, which has a Python site (just the smallest VDS, he did not master the python from memory). The main domain is linked to the VDS server IP, let's call it domain.ru. One of the subdomains is required to contact my IP. That is, domain.ru is on IP VDS, sub.domain.ru is mine. The task seems to be simple, but then the fun begins.
$TTL 3600 <br/> domain.ru. IN SOA ns1.firstvds.ru. root.domain.ru. (2010090201 10800 3600 604800 86400) <br/> domain.ru. IN NS ns1.firstvds.ru. <br/> domain.ru. IN NS ns2.firstvds.ru. <br/> domain.ru. IN NS ns3.firstvds.ru. <br/> domain.ru. IN MX 10 mail <br/> domain.ru. IN MX 20 mail <br/> domain.ru. IN A [IP VDS] <br/> www IN A [IP VDS] <br/> ftp IN A [IP VDS] <br/> mail IN A [IP VDS] <br/> smtp IN A [IP VDS] <br/> pop IN A [IP VDS] <br/> sub IN A [IP своего сервера] # - все самое интересное здесь
I figured it all out, the zone ID in the first line is also constantly changing as expected. bind has been restarted, after a few hours the DNS has been updated, and if via SSH with VDS, do:
root: ~ # host sub.domain.ru
sub.domain.ru A [IP of my server]
And, it would seem, everything is fine. Only here every 3-4 hours (when DNS'ki updated), it changes the IP. That subdomain has the old IP then the new one. This is how it looks from my car (the console shows the time, you can trace it):
[21:24:05]:[email protected] ~>nslookup sub.domain.ru<br/> Server: 192.168.0.1<br/> Address: 192.168.0.1#53<br/> <br/> Non-authoritative answer:<br/> Name: sub.domain.ru<br/> Address: [новый IP]<br/> <br/> [23:26:06]:[email protected] ~>nslookup sub.domain.ru<br/> Server: 192.168.0.1<br/> Address: 192.168.0.1#53<br/> <br/> Non-authoritative answer:<br/> Name: sub.domain.ru<br/> Address: [старый IP, который на VDS]
So you see that DNS is jumping back and forth. After a few hours it becomes normal again, then the old one again. The site will start soon, so I would like to get rid of it. And I myself do it for the first time, since I don’t trump the admin. I even tried to delete a domain through ISPManager and add it again. The same crap, and sometimes both IPs come to the Non-authoritative answer at once.
This has been happening for more than a month. Changed the zone file many times. In support of FirstVDS, I don’t even know whether to contact, as they always say “your server is your problem” and advise you to reinstall everything.
PS: Immediately apologize for the fictional domains, I hope clearly explained.
And so - edited the file with handles or through ISPmanager? It is necessary through ISPmanager, as it changes the series of the zone and notifies external servers that it would not be bad to update the domain information.
Shl: ns3.firstvds.ru does not exist - it is better to remove it (and from the ISPmanager settings)
Now I will delete too much, let's see, thanks for the answer. If anything, we will contact the support, although I really do not like to do it. - rithika kancharla
In general, I understood a long time ago that a self-compiled DNS server is not a rewarding business. It is much easier to get a DNS server for a whole year for 40 eurocents and not to bathe.
Then there are a couple of questions:
1. Do you have your dns server on VDS? Then why is there no him in the zone?
2. If this is not the case, then in the firstvds web interface you can indicate that their dns will be like a slave?
3. a) If yes, then do your master, their slave
b) If not, then try, if there is an opportunity, to make your own slave for them and see what the zone looks like at the moment of changing ip and, what is the most important thing, which key?
If I misunderstand you - ask. If you have questions - write;)
2) I have not seen this even. Just a list of servers. - theophanu
#dig domain.ru ns + noqr + short
Just used to operate only with my own dns =)
3) I can, in an extreme case, offer to slap a slave zone on my server, and master on my VDS =) blockquote> $ - amerydbaker
2) dig the same data? ISPManager now for the sake of development I will look, maybe I can think of it.
There is just another feeling that they themselves had masters / slaves after a liter tuned :) - dylan lysen
so here. - jim keith
produces the same thing? - stephanie adams
dig sub.domain.ru @ ns1 | 2 | 3.firstvds.ru + short
but I think you understand me. - karen mcp
a picture of what you are doing changes on the secondary, and the primary in 3 hours rubs your notes.
I mean, what to do with pens and always on Primari ns1.firstvds.ru
write a record, change the series, it is written as a date and at the end the change number (from 00 - 99) which number is not so important, the main thing that it differs from the previously entered, the date is also not desirable to change.
try a record like this
sub.domain.ru. A ipaddr
note after the full spelling of the domain is worth a point.
The series I know how to prescribe, and through the manager he generates it himself, so everything should be ok with him.
I will try this entry now, thanks. - vedrana
domain.ru. IN MX 10 mail
domain.ru. IN MX 20 mail
that's bullshit. Why are you two identical server in mx indicated? What do you really expect? What mail server will knock 2 times on one server? No, after the first failure, he will stop trying in this case.
Your problem is really easy. I think a caliper could help.
You can diagnose yourself: for this you need to ask about sub.domain.ru. all name servers specified for domain.ru. The list of these servers can be obtained from the command line using the command
Please note that it may not coincide with
domain.ru. IN NS ns1.firstvds.ru.
domain.ru. IN NS ns2.firstvds.ru.
domain.ru. IN NS ns3.firstvds.ru.
When you find out, check the A-record on each of this list, for example:
nslookup sub.domain.ru. ns3.firstvds.ru.
if there is a mistake somewhere - correct
who.is/whois/domain.ru/ - dinar
I have archlinux, it could be understood by the logs from the console.
I went to diagnose, thanks for the minus. - lorna dh
In general, apparently some of the above methods helped. All ns say the correct IP. We will observe more, I hope everything will work.
Thanked in karma. - bookmaniac70