logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

Strange problem when updating zone files: msg#00335

Subject: Strange problem when updating zone files
Hi!

I've searched the archives but havent been able to find an answer :-/

Problem:

I change something in zone file for ANY domain on my primary dns server (which 
handles the same domains as my secondary dns server).

Primary ns: ns.ipv6shells.com
Secondary: backup-dns.dk

Example:
I add A record localhost.ipv6shells.com to zone file and update serial.
Restart primary NS server. Nothing happens on backup-dns.dk (!!)... However I 
get the following in the primary dns log:

Jan 23 23:09:20 linux named[7045]: lame server resolving 'backup-dns.dk' (in 
'backup-dns.dk'?): 80.199.16.132#53

Now if I restart the secondary dns server (not making ANY changes on either the 
primary and/or the secondary) I get the following:

Primary dns log:
Jan 23 23:13:00 linux named[7045]: client 80.199.16.132#28196: transfer of 
'ipv6shells.com/IN': AXFR-style IXFR started

Secondary dns log:
Jan 23 23:12:37 firewall named[18872]: transfer of 'ipv6shells.com/IN' from 
80.62.64.130#53: end of transfer

The primary ns has its own dedicated wan ip and port 53 fully open both tcp/udp.
The secondary ns is behind NAT but has had both port 53 tcp AND udp natted in 
to it.

What is going on? :-(

Best Regards
-Rasmus Haslund





<Prev in Thread] Current Thread [Next in Thread>