hits on 113 from secondary nameserver??

N

Nybbles

[H]ard|Gawd
Joined
Jun 17, 2002
Messages
1,234
Ok, so I'm hosting a couple domains on a server on my DSL line (Speakeasy 1.5/768). I run a primary name server for those domains here, and use EveryDNS as a secondary nameserver for those domains.

Well ever since I've set this secondary up with them I have been getting hits from axfr.everydns.net which they use to do the zone transfer. I get about 80-90 hits on TCP port 113 from it.

I emailed support and asked if this should be something that I should be opening up, although I dont know why I would need to. They had no idea why I'm getting these hits.

So does anyone know why initiating a zone transfer would cause a secondary nameserver to hit tcp port 113??

EDIT: Correction, about 190 hits on the firewall per 24 hour period.
 
But would a zone transfer need port 113???

That's what i dont understand. And even with those packets blocked at the firewall. my zones are still consistent across the servers so they are still getting transfered.

I'll probably just open that port up to that IP only so they will stop cluttering up my logs. sheesh.

Oh well. Thanks!
 
You must log in or register to reply here.
Back
Top