<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
It seems it's taking some time to sync after the transfer, because
now it resolves ok with the new data.<br>
<br>
nslookup 192.168.250.101 192.168.2.251<br>
Server: 192.168.2.251<br>
Address: 192.168.2.251#53<br>
<br>
101.250.168.192.in-addr.arpa name = openerp-bold.vi.pt.<br>
<br>
<br>
nslookup 192.168.250.101 192.168.2.252<br>
Server: 192.168.2.252<br>
Address: 192.168.2.252#53<br>
<br>
101.250.168.192.in-addr.arpa name = openerp-bold.vi.pt.<br>
<br>
<br>
After the transfer i checked the new zone file and it was exactly
the same as the master one.<br>
<br>
If i make a new change to the master how can i then check if
101.250.168.192.in-addr.arpa PTR is cached?<br>
<br>
<br>
<div class="moz-cite-prefix">On 24-07-2014 15:35, John Miller wrote:<br>
</div>
<blockquote
cite="mid:CAGYMsbstjvzOVjtnYpnQnznpEkK5WsZeZRsv-gZ50k0Mhd=EZw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>On NS #2, if you run rndc freeze/rndc thaw, what does the
actual zone file look like? Also, what does your cache look
like? Is 101.250.168.192.in-addr.arpa PTR cached?<br>
<br>
</div>
John<br>
</div>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On Thu, Jul 24, 2014 at 10:25 AM,
Ricardo Esteves <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:maverick.pt@gmail.com" target="_blank">maverick.pt@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi,<br>
<br>
I've got two bind9 servers, one master (192.168.2.251) and
one slave (192.168.2.252).<br>
<br>
I've configured zone transfers, and after a change of a
zone on the master, the slave gets the notification,
downloads successfully the new zone file, but still has
the old information in memory:<br>
<br>
nslookup 192.168.250.101 <b>192.168.2.251</b><br>
Server: 192.168.2.251<br>
Address: 192.168.2.251#53<br>
<br>
<b>101.250.168.192.in-addr.arpa name = <a
moz-do-not-send="true"
href="http://openerp-bold.xpto.com" target="_blank">openerp-bold.xpto.com</a>.</b><br>
<br>
nslookup 192.168.250.101 <b>192.168.2.252</b><br>
Server: 192.168.2.252<br>
Address: 192.168.2.252#53<br>
<br>
<b>101.250.168.192.in-addr.arpa name = <a
moz-do-not-send="true"
href="http://demoopenerp1.xpto.com" target="_blank">demoopenerp1.xpto.com</a>.</b><br>
<br>
----------------------<br>
<br>
Log on the slave:<br>
<br>
24-Jul-2014 14:48:42.481 notify: info: client
192.168.2.251#61865: view vi_local_resolver: received
notify for zone '250.168.192.in-addr.arpa'<br>
24-Jul-2014 14:48:42.481 general: info: master
192.168.2.251#53 (source 192.168.2.252#0) deleted from
unreachable cache<br>
24-Jul-2014 14:48:42.482 general: debug 1:
queue_soa_query: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.482 general: debug 1: soa_query: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.482 general: debug 3:
dns_request_createvia<br>
24-Jul-2014 14:48:42.482 general: debug 3: request_render<br>
24-Jul-2014 14:48:42.482 general: debug 3:
requestmgr_attach: 0x801f11170: eref 1 iref 1<br>
24-Jul-2014 14:48:42.482 general: debug 3: mgr_gethash<br>
24-Jul-2014 14:48:42.482 general: debug 3: req_send:
request 0x8037eaea8<br>
24-Jul-2014 14:48:42.482 general: debug 3:
dns_request_createvia: request 0x8037eaea8<br>
24-Jul-2014 14:48:42.482 general: debug 3: req_senddone:
request 0x8037eaea8<br>
24-Jul-2014 14:48:42.483 general: debug 3: req_response:
request 0x8037eaea8: success<br>
24-Jul-2014 14:48:42.483 general: debug 3: req_cancel:
request 0x8037eaea8<br>
24-Jul-2014 14:48:42.483 general: debug 3: req_sendevent:
request 0x8037eaea8<br>
24-Jul-2014 14:48:42.483 general: debug 1:
refresh_callback: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.483 general: debug 3:
dns_request_getresponse: request 0x8037eaea8<br>
24-Jul-2014 14:48:42.483 general: debug 1:
refresh_callback: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: serial: new
2014072417, old 2014070617<br>
24-Jul-2014 14:48:42.483 general: debug 3:
dns_request_destroy: request 0x8037eaea8<br>
24-Jul-2014 14:48:42.483 general: debug 3: req_destroy:
request 0x8037eaea8<br>
24-Jul-2014 14:48:42.483 general: debug 3:
requestmgr_detach: 0x801f11170: eref 1 iref 0<br>
24-Jul-2014 14:48:42.483 general: debug 1: queue_xfrin:
zone 250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.484 general: info: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: Transfer
started.<br>
24-Jul-2014 14:48:42.484 general: debug 1: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: requesting
IXFR from 192.168.2.251#53<br>
24-Jul-2014 14:48:42.484 xfer-in: info: transfer of
'250.168.192.in-addr.arpa/IN/vi_local_resolver' from
192.168.2.251#53: connected using 192.168.2.252#51302<br>
24-Jul-2014 14:48:42.484 xfer-in: debug 3: transfer of
'250.168.192.in-addr.arpa/IN/vi_local_resolver' from
192.168.2.251#53: requesting IXFR for serial 2014070617<br>
24-Jul-2014 14:48:42.484 xfer-in: debug 3: transfer of
'250.168.192.in-addr.arpa/IN/vi_local_resolver' from
192.168.2.251#53: sent request length prefix<br>
24-Jul-2014 14:48:42.484 xfer-in: debug 3: transfer of
'250.168.192.in-addr.arpa/IN/vi_local_resolver' from
192.168.2.251#53: sent request data<br>
24-Jul-2014 14:48:42.486 xfer-in: debug 3: transfer of
'250.168.192.in-addr.arpa/IN/vi_local_resolver' from
192.168.2.251#53: got nonincremental response<br>
24-Jul-2014 14:48:42.486 general: debug 1: zone_settimer:
zone 250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.486 general: debug 3: removing
journal file<br>
24-Jul-2014 14:48:42.486 general: debug 3: replacing zone
database<br>
24-Jul-2014 14:48:42.486 general: debug 1: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: zone
transfer finished: success<br>
24-Jul-2014 14:48:42.486 general: info: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: transferred
serial 2014072417<br>
24-Jul-2014 14:48:42.486 general: debug 1: zone_settimer:
zone 250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.486 xfer-in: info: transfer of
'250.168.192.in-addr.arpa/IN/vi_local_resolver' from
192.168.2.251#53: Transfer completed: 1 messages, 12
records, 416 bytes, 0.001 secs (416000 bytes/sec)<br>
24-Jul-2014 14:48:42.486 general: debug 1: zone_timer:
zone 250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.486 general: debug 1:
zone_maintenance: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.486 general: debug 1: zone_dump: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.486 general: debug 1: zone_settimer:
zone 250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.486 general: debug 1:
zone_gotwritehandle: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.490 general: debug 1: dump_done: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver: enter<br>
24-Jul-2014 14:48:42.490 general: debug 3: zone
250.168.192.in-addr.arpa/IN/vi_local_resolver:
dns_journal_compact: not found<br>
<br>
--------------------<br>
<br>
Anyone has any idea what could be wrong?<br>
<br>
Best regards,<br>
Ricardo Esteves.<br>
<br>
</div>
<br>
_______________________________________________<br>
Please visit <a moz-do-not-send="true"
href="https://lists.isc.org/mailman/listinfo/bind-users"
target="_blank">https://lists.isc.org/mailman/listinfo/bind-users</a>
to unsubscribe from this list<br>
<br>
bind-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a><br>
<a moz-do-not-send="true"
href="https://lists.isc.org/mailman/listinfo/bind-users"
target="_blank">https://lists.isc.org/mailman/listinfo/bind-users</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
John Miller<br>
Systems Engineer<br>
Brandeis University<br>
<a moz-do-not-send="true" href="mailto:johnmill@brandeis.edu">johnmill@brandeis.edu</a><br>
(781) 736-4619
</div>
</blockquote>
<br>
</body>
</html>