RFC-1035 explanation needed
Hi, I read below paragraph from RFC 1035 about AXFR: " - If the server needs to close a dormant connection to reclaim resources, it should wait until the connection has been idle for a period on the order of two minutes. In particular, the server should allow the SOA and AXFR request sequence (which begins a refresh operation) to be made on a single connection. Since the server would be unable to answer queries anyway, a unilateral close or reset may be used instead of a graceful close." What does it means by "since the server would be unable to answer queries." ? And when "reset.." should be used? Regards, Alans ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
view and dynamic zone updated by dhcp
Hello, I have two servers bind9 and dhcpdv3 with dynamic update for a specific zone and a few other standard zones, but actually without view. All my setup works great, but when I have tried to add view, problem... I explain how. I setup three views and in these 3 views, I need to have the dynamic zone inside. When I do this, I see in the syslog message 4 requests to add the dns entry in the zone file and 4 errors in the specific bind file log as follow : * general: error: malformed transaction: /var/zones/example.com.jnl last serial 2008198936 != transaction first serial 2008198864 ** I could make with these errors, but the update is not done for the dynamic zone file. Could someone help me to find why and how I could do this please ? Regards Jean ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: view and dynamic zone updated by dhcp
My bet is that you are sharing the master file of the zone being updated between views/zones. Don't do that. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: view and dynamic zone updated by dhcp
Hello, thank you for your reply, but I don't understand how I could do this in an another way. I need that all views could reach the dynamic zone... Jean 2010/2/17 Mark Andrews > > My bet is that you are sharing the master file of the zone being updated > between views/zones. Don't do that. > > Mark > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org > -- Meilleures salutations Jean Chiappini ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: view and dynamic zone updated by dhcp
In message <9fe68cb21002170541n3938e4f2r2cbc494f798b7...@mail.gmail.com>, Jean Chiappini writes: > Hello, > > thank you for your reply, but I don't understand how I could do this in an > another way. I need that all views could reach the dynamic zone... > > Jean transfer the zone between views. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: view and dynamic zone updated by dhcp
Could you give me an example of that please. 2010/2/17 Mark Andrews > > In message <9fe68cb21002170541n3938e4f2r2cbc494f798b7...@mail.gmail.com>, > Jean > Chiappini writes: > > Hello, > > > > thank you for your reply, but I don't understand how I could do this in > an > > another way. I need that all views could reach the dynamic zone... > > > > Jean > > transfer the zone between views. > > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org > -- Meilleures salutations Jean Chiappini ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: RFC-1035 explanation needed
On 2/17/2010 3:05 AM, Alans wrote: Hi, I read below paragraph from RFC 1035 about AXFR: " - If the server needs to close a dormant connection to reclaim resources, it should wait until the connection has been idle for a period on the order of two minutes. In particular, the server should allow the SOA and AXFR request sequence (which begins a refresh operation) to be made on a single connection. Since the server would be unable to answer queries anyway, a unilateral close or reset may be used instead of a graceful close." What does it means by "since the server would be unable to answer queries..." ? And when "reset.." should be used? If I were to speculate, I'd say that the author was imagining a situation where the nameserver was experiencing such severe resource starvation that it couldn't even respond to UDP queries until it reclaimed a dormant TCP connection, its associated buffers, control blocks, etc. Remember, this was written back in 1987. Machines struggled with memory management back then, and networking stacks were pretty primitive. Also, the apparent hope/expectation of the author was that DNS resolvers would typically maintain persistent TCP connections to DNS servers, but this never materialized, since it's a lot harder to manage a bunch of persistent TCP connections than short-lived UDP transactions, and there's no real performance benefit to be gained over (what came to be the _de_facto_ standard of) UDP-with-TCP-fallback-on-truncation, given the name-lookup usage patterns which evolved over time. I'm not sure that modern BIND even has any code in it to reclaim dormant TCP connections, since no resolvers (of which I'm aware) maintain persistent TCP connections. If there is such code, it's probably only for compliance with the aforementioned verbiage in the standard, not because it would actually see much practical use in the real world... - Kevin ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
