Feb 13 09:01:22.663 dispatch: dispatch 0x3fdcc088: shutting down due to TCP
receive error: connection reset
What do these really mean? Is that hex after the second instance of 'dispatch'
meaningful to an admin or only to a BIND codemonkey? Not that there's anything
wrong with codemonkies, I'm
Hello,
Before I had bind-9.5.0-P2 and now I upgrade to bind-9.5.1. I readed that in
bind-9.5.1 is additional support for query port randomization
including performance improvement and port range specification.
But is this ok?
netstat
udp0 0 ls1.tel.net.ba:29825203.64
Before I had bind-9.5.0-P2 and now I upgrade to bind-9.5.1. I readed that in
bind-9.5.1 is additional support for query port randomization
including performance improvement and port range specification.
But is this ok?
netstat
udp0 0 ls1.tel.net.ba:29825203.64.139.9:domain
I'm trying to delegate a subdomain to a server that is not directly
accessible from the internet, yet be able to resolve names in the
subdomain from the internet. I understood 'forwarding' would be the
solution but I can't get it to work completely:
I have on both ns1 and ns2 which are authorit
JINMEI Tatuya / 神明達哉 wrote:
> At Fri, 06 Feb 2009 21:36:18 -0500,
> David Ford wrote:
>
> You specify the IP address of the NS in question as bogon. That
> should be the reason for the SERVFAIL.
>
>
>> acl "bogon" {
>>
> ...
>
>> 174.0.0.0/8;
>>
> ...
>
>> };
>>
>>
The zone forwarder you put in the conf of ns1/ns2 are only going to work for
people actually using ns1/ns2 as their resolver. This is why when you get
on a remote client and actually dig ns1 for the subdomain it works.
However, when someone on the Internet as a whole asks for
something.sub.company
What youre seeing is ports your server has opened for queries. Then it
holds the port open while waiting for a reply and for some time after that.
For example, FROM ls1.tel.net.ba:29825 TO 203.64.139.9:domain. By design, if
someone does a lot of queries to crackerjack.net, your server is going to
At Fri, 13 Feb 2009 09:50:17 -0600,
"Laws, Peter C." wrote:
> Feb 13 09:01:22.663 dispatch: dispatch 0x3fdcc088: shutting down due to TCP
> receive error: connection reset
>
> What do these really mean? Is that hex after the second instance of
Most likely a remote authoritative server closed
Just as there is a "default-less core" to Internet routing, there is
also a "forwarding-less core" to Internet DNS, and your nameservers --
congratulations -- are in that core. The queries you get from other
nameservers in the core are non-recursive, defined to mean "give me
whatever informatio
At Fri, 13 Feb 2009 19:10:02 +0100,
"Elizabeta Zadro" wrote:
> Before I had bind-9.5.0-P2 and now I upgrade to bind-9.5.1. I readed that in
> bind-9.5.1 is additional support for query port randomization
>
> including performance improvement and port range specification.
>
> But is this ok?
[
Setting up a slave NS to a master with multiple views. One view is
public, the other is only handed out to a sandbox set of IPs
(registration network).
This older article
http://www.oreillynet.com/pub/a/oreilly/networking/news/views_0501.html
seems to indicate that the only way to get the sla
Jeffrey Collyer wrote:
> This older article
> http://www.oreillynet.com/pub/a/oreilly/networking/news/views_0501.html
>
> seems to indicate that the only way to get the slave to fully sync the
> zones in both views is to create a virtual IP on the slave (with an IP
> in the sandbox range) so the
Thanks all for the clear explanation.
If I understand correctly:
- forwarding is not a solution to my problem. (even the suggestion by
Chris didn't help)
- having ns1/ns2 slave from devbox would be a solution (but in my
specific case I can't because devbox runs a custom nameserver based on
Anyone ever see this error with Bind running on Windows?
I only could find one reference to this in Google and it looks like he never
got an answer :-P
[d:\bind\bin]named -g
13-Feb-2009 22:16:57.082 starting BIND 9.6.0-P1 -g
13-Feb-2009 22:16:57.102 built with default
13-Feb-2009 22:16:57.102 fo
On 13 fév, 20:15, "Mike Bernhardt" wrote:
> What you=92re seeing is ports your server has opened for queries. Then it
> holds the port open while waiting for a reply and for some time after that.
> For example, FROM ls1.tel.net.ba:29825=A0TO 203.64.139.9:domain. By design,=
> if
> someone does a
kenk...@yahoo.com wrote:
> Anyone ever see this error with Bind running on Windows?
> I only could find one reference to this in Google and it looks like he never
> got an answer :-P
>
> [d:\bind\bin]named -g
> 13-Feb-2009 22:16:57.082 starting BIND 9.6.0-P1 -g
> 13-Feb-2009 22:16:57.102 built wi
At Mon, 9 Feb 2009 20:11:20 -0500, Peter Fraser wrote:
>
> HI All
> I have been working to get dynamic updates working with bind-9.5 and
> FreeBSD 7 So far I have done the following:
>
> 1. COmpiled bind with GSSAPI enabled.
> 2. Added these to named.conf
>
> options {
>...
> tke
17 matches
Mail list logo