[lug] DNS

[Harris, James]

Sorry that was a bit more brief than I intended.

I'm guessing that this is caused by the slave not being able to refresh the
zone data with the master.  If you know for fact that the master is up and
working fine, then I would look to a possible communication problem.  On
some firewalls I've seen people open up the necessary UDP ports for
communication, but not the TCP ports which are used for zone transfers.

-----Original Message-----
From: Harris, James [mailto:James_Harris at maxtor.com] 
Sent: Monday, January 14, 2002 15:39
To: 'lug at lug.boulder.co.us'
Subject: RE: [lug] DNS


Possible network communication?  Make sure you can talk TCP between the
master and the slave

-----Original Message-----
From: Shannon Johnston [mailto:sjohnston at cavion.com] 
Sent: Monday, January 14, 2002 16:24
To: lug at lug.boulder.co.us
Subject: [lug] DNS


Does anybody know what would cause this in a slave Bind 9.1.3 server. I get
this a bunch of times when I restart the named service.


refresh_callback: zone domain.com/IN: failure for <IPADDR_MASTER>#53: timed
out


_______________________________________________
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
_______________________________________________
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug