dns sync problem

[pcoeman]

Hi,

Since a few days I have a dns sync error (again). My domain: antifa.net. My dns: prim: ns1.antifa.net & s2.ezzi.net. When I create a now domain or subdomain they are not resolve on s2. When I dig I find the data on ns1. examples:

-yabasta.antifa.be
-a2k2.antifa.net

both created days ago. NS1 is bind 8.3.6 and s2 is bind 8.4.4.

Second strange thing: ns1.antifa.net is the pri dns, s2.ezzi.net is the sec dns. But it seems that the data stored on s2 is propagated to the world, not ns1. Otherwise; I think, these domains should be availble because digging ns1 gives the somain responses.

 

[nobaloney]

Did you see the error at DNS reports? See it here.

How do you have the domain set up on s2.ezzi.net? Do you have it set up as a slave?

if so, how does it know what records to slave? Does it have a record in the named.conf file directing it where to get the master record from?

Does it properly replicate the master record?

Or did you just create a duplicate master zone at s2.ezzi.net?

Do you have separate zones created by DA for yabasta.antifa.be and for a2k2.antifa.net on ns1.antifa.net, or do you have records for yabasta in the antifa.be zone file and for a2k2 in the antifa.net zone file?

If you've got a separate zone file for the subdomain, then you should have ns records for the subdomain in the zone file for the main domain. DA does NOT set them by default. And slaving will NOT work properly unless they're set.

Jeff

 

[pcoeman]

Did you see the error at DNS reports? See it here.

How do you have the domain set up on s2.ezzi.net? Do you have it set up as a slave?

if so, how does it know what records to slave? Does it have a record in the named.conf file directing it where to get the master record from?

Does it properly replicate the master record?

Or did you just create a duplicate master zone at s2.ezzi.net?

Do you have separate zones created by DA for yabasta.antifa.be and for a2k2.antifa.net on ns1.antifa.net, or do you have records for yabasta in the antifa.be zone file and for a2k2 in the antifa.net zone file?

If you've got a separate zone file for the subdomain, then you should have ns records for the subdomain in the zone file for the main domain. DA does NOT set them by default. And slaving will NOT work properly unless they're set.

Jeff

This is a lot of questions. Does this mean that DA is not a automated system. I hated plesk for a lot of reasons, but the only thing that worked was dns... Anyway, I seems that some basic skills to run dns and DA is not enough. I go to the book shop tomorow to fight with dns in dept

Thanks for yor time Jeff!

 

[pcoeman]

Did you see the error at DNS reports? See it here.

How do you have the domain set up on s2.ezzi.net? Do you have it set up as a slave?

if so, how does it know what records to slave? Does it have a record in the named.conf file directing it where to get the master record from?

Does it properly replicate the master record?

Or did you just create a duplicate master zone at s2.ezzi.net?

Do you have separate zones created by DA for yabasta.antifa.be and for a2k2.antifa.net on ns1.antifa.net, or do you have records for yabasta in the antifa.be zone file and for a2k2 in the antifa.net zone file?

If you've got a separate zone file for the subdomain, then you should have ns records for the subdomain in the zone file for the main domain. DA does NOT set them by default. And slaving will NOT work properly unless they're set.

Jeff

1. s2.ezzi.net is setup as slave domain.
2. I only have asccess to s2.ezzi.net via webmin. This is the info I found op s2 for antifa.be:

$ORIGIN be.
antifa 14400 IN SOA ns1.antifa.net. root.antifa.be. (
2004081700 7200 3600 1209600 86400 )
14400 IN NS ns1.antifa.net.
14400 IN NS s2.ezzi.net.
14400 IN A 66.199.224.99
14400 IN TXT "v=spf1 ~all"
14400 IN MX 10 mail.antifa.be.
$ORIGIN antifa.be.
pop 14400 IN A 66.199.224.99
mail 14400 IN A 66.199.224.99
localhost 14400 IN A 127.0.0.1
ftp 14400 IN A 66.199.224.99
www 14400 IN A 66.199.224.99

I didn't duplicate the master record. I created it as a slave for ns1.antifa.net and a few minutes after all was replicated.

3. I let DA do all the job. I did nothing. This is the yabasta dns record on my server:

ftp A 66.199.224.99
localhost A 127.0.0.1
mail A 66.199.224.99
pop A 66.199.224.99
www A 66.199.224.99
yabasta.antifa.be. A 66.199.224.99
yabasta.antifa.be. NS ns1.antifa.net.
yabasta.antifa.be. NS s2.ezzi.net.
mail MX 10

yabasta.antifa.be is not known on s2.ezzi.net. Force synchrionize gives no effect.

 

[nobaloney]

1. s2.ezzi.net is setup as slave domain.

I'm not sure what you mean. I thought s2.ezzi.net was the name of a nameserver? Is it also the name of a domain hosted on the second server?

2. I only have asccess to s2.ezzi.net via webmin. This is the info I found op s2 for antifa.be:

$ORIGIN be.
antifa 14400 IN SOA ns1.antifa.net. root.antifa.be. (
2004081700 7200 3600 1209600 86400 )
14400 IN NS ns1.antifa.net.
14400 IN NS s2.ezzi.net.
14400 IN A 66.199.224.99
14400 IN TXT "v=spf1 ~all"
14400 IN MX 10 mail.antifa.be.
$ORIGIN antifa.be.
pop 14400 IN A 66.199.224.99
mail 14400 IN A 66.199.224.99
localhost 14400 IN A 127.0.0.1
ftp 14400 IN A 66.199.224.99
www 14400 IN A 66.199.224.99

Note that there's no record for "yabasta.antifa.be".

Is there a separate zone file for "yabasta.antifa.be"? If not, then of course the slave-server won't have any information for it.

There are two "official ways" to get yabasta.antifa.be to show up.

1) Insert a record for yabasta into the antifa.be domain zone file on the master server.

2) Create a new zone (with all the necessary records) for yabasta.antifa.be on the master server, and create ns records for yabasta.antifa.be as part of the antifa.be zone file.

Unfortunately DA uses only a part of the second method. They create the new zone file but they do NOT create the NS entries in the parent zone file (in this case they do not create NS records for yabasta in the antifa.be zone).

So the slave zone file may not show up.

If it doesn't, one way to solve the problem is to create the NS records in your antifa.be zone file. Another way would be to create the A record (and other necessary records) for yabasta in the antifa.be master zone file.

I didn't duplicate the master record. I created it as a slave for ns1.antifa.net and a few minutes after all was replicated.

Perhaps all wasn't replicated. Check for a zone file for yabasta.antifa.be.

3. I let DA do all the job. I did nothing. This is the yabasta dns record on my server:

ftp A 66.199.224.99
localhost A 127.0.0.1
mail A 66.199.224.99
pop A 66.199.224.99
www A 66.199.224.99
yabasta.antifa.be. A 66.199.224.99
yabasta.antifa.be. NS ns1.antifa.net.
yabasta.antifa.be. NS s2.ezzi.net.
mail MX 10

yabasta.antifa.be is not known on s2.ezzi.net.

Probably because the zone file wasn't copied. As I wrote above, most likely because there are no ns records for yabasta in the antifa.be master zone file.

You can fix it either of the two ways I've mentioned.

And we can all nicely ask DA to amend their procedure so slave DNS will work properly.

Jeff