Re: S-NAPTR and lightweight resolver
On Sat, May 09, 2009 at 09:38:25AM +1000, Mark Andrews mark_andr...@isc.org wrote a message of 26 lines which said: It is up to the application to sort and process the returned records. But I suspect that this is precisely what the OP wanted (and expected BIND to do). Does anyone know a good free-software library for processing NAPTR/S-NAPTR/U-NAPTR records? ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Semi-OT, BIND dlz and excessive queries
The DLZ users mailing list is pretty quiet, thought to ask here in case someone can elaborate. I have MySql query logging on so I can see the queries as they come in for testing. dig example.com @localhost This yields a hit to the database of 090509 5:50:56 2593 Query SELECT zone FROM resource_records WHERE zone = 'example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'com' Two hits. dig a.b.c.d.f.g.h.i.j.k.l.m.n.o.p.q.r.s.t.u.v.w.x.y.z.example.com @localhost A Small snip of the log for that one, I am sure you get the idea: 2593 Query SELECT zone FROM resource_records WHERE zone = 's.t.u.v.w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 't.u.v.w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'u.v.w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'v.w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'com' Is this expected behavior? This seems quite a simple way to potentially bring a data source to it's knees. -- Scott * If you contact me off list replace talklists@ with scott@ * ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Semi-OT, BIND dlz and excessive queries
afaik, yes it's expected - for the reason that we don't yet have a smart way across all types of database to find the most specific match without doing multiple queries. -david Scott Haneda wrote: The DLZ users mailing list is pretty quiet, thought to ask here in case someone can elaborate. I have MySql query logging on so I can see the queries as they come in for testing. dig example.com @localhost This yields a hit to the database of 090509 5:50:56 2593 Query SELECT zone FROM resource_records WHERE zone = 'example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'com' Two hits. dig a.b.c.d.f.g.h.i.j.k.l.m.n.o.p.q.r.s.t.u.v.w.x.y.z.example.com @localhost A Small snip of the log for that one, I am sure you get the idea: 2593 Query SELECT zone FROM resource_records WHERE zone = 's.t.u.v.w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 't.u.v.w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'u.v.w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'v.w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'w.x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'x.y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'y.z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'z.example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'example.com' 2593 Query SELECT zone FROM resource_records WHERE zone = 'com' Is this expected behavior? This seems quite a simple way to potentially bring a data source to it's knees. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
socket.c:4524: unexpected error
Hello, I've been seeing more and more of the following errors in all of our name servers running Bind 9.4.3-2 on CentOS 5.3 servers: May 8 11:00:44 ns3 named[7502]: socket.c:4524: unexpected error: May 8 11:00:44 ns3 named[7502]: 22/Invalid argument May 8 11:00:45 ns3 named[7502]: socket.c:4524: unexpected error: May 8 11:00:45 ns3 named[7502]: 22/Invalid argument May 8 11:00:45 ns3 named[7502]: socket.c:4524: unexpected error: May 8 11:00:45 ns3 named[7502]: 22/Invalid argument May 8 11:00:45 ns3 named[7502]: socket.c:4524: unexpected error: May 8 11:00:45 ns3 named[7502]: 22/Invalid argument May 8 11:00:50 ns3 named[7502]: socket.c:4524: unexpected error: May 8 11:00:50 ns3 named[7502]: 22/Invalid argument May 8 11:00:51 ns3 named[7502]: socket.c:4524: unexpected error: May 8 11:00:51 ns3 named[7502]: 22/Invalid argument May 8 11:00:51 ns3 named[7502]: socket.c:4524: unexpected error: May 8 11:00:51 ns3 named[7502]: 22/Invalid argument May 8 11:00:52 ns3 named[7502]: socket.c:4524: unexpected error: May 8 11:00:52 ns3 named[7502]: 22/Invalid argument May 8 11:00:52 ns3 named[7502]: socket.c:4524: unexpected error: thx, SW ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
