Problem with DNS

Question

Domain Name System

Problem with DNS for some users.

Good afternoon!
There is a site that recently transferred it to another server (in the same data center), which led to a change in its IP. DNS servers remain the same.
Apparently, this caused some problems - 5 people have already contacted me today and reported, but their site does not open.

It turned out that the problem is that the domain does not resolve on the DNS servers of some providers:

For example, here is one of the problematic provider DNS: 94.242.1.4 nslookup
mmoboom.ru At the same time, the rest of the domains resolve normally. At the same time, nslookup mmoboom.ru 8.8.8.8 gives a Non-authoritative answer: Name: mmoboom.ru Address: 95.169.190.235 The site traffic has not dropped much, therefore, I suspect that the problem is some kind of local character. However, the fact that not one person wrote to me, but as many as 5 also suggests that the problem, nevertheless, is somewhere with me. Zone config on DNS server:



$TTL 604800
@ IN SOA localhost. root.localhost. (
2011070601 ; Serial
1h ; Refresh
1h ; Retry
1w ; Expire
1d ) ; minimum
;
@ IN NS ns1.mmoboom.ru.
@ IN NS ns2.mmoboom.ru.
@ IN MX 1 aspmx.l.google.com.
@ IN MX 3 alt1.aspmx.l.google.com.
@ IN MX 3 alt2.aspmx.l.google.com.
@ IN MX 5 aspmx2.googlemail.com.
@ IN MX 5 aspmx3.googlemail.com.
@ IN MX 5 aspmx4.googlemail.com.
@ IN MX 5 aspmx5.googlemail.com.

@ IN A 95.169.190.235
mx IN A 95.169.190.235
* IN A 95.169.190.235
ts3 IN A 95.169.191.225
mumble IN A 95.169.191.225
www IN CNAME @
mail IN CNAME ghs.google.com.

Of the obvious problems - both NS domain servers are located on the same physical server (but on different subnets), however:
1. There are no problems on the server and there were no problems.
2. Other sites that are located on the same server as the problematic one and also have the same set of NS servers open perfectly for those people who experience problems with mmoboom.ru

The questions are actually obvious: What else could be the problem? Where to dig?

UPDATE: Resolved
The problem was that there were no A records on ns1 and ns2. Therefore, ns1.mmoboom.ru and ns2.mmoboom.ru resolved as 95.169.190.235, where there is not even a bind :) NS servers and the site were on the same machine.

Answer 1

I don't see any particular problems.
thednsreport.com/?domain=mmoboom.ru
ttl is only very cosmic. Do 'rndc retransfer mmoboom.ru' on the slave server.