namednamed
It could be something simple that I am missing.. we'll well see. Any
thoughts? Thanks for your help,
AJ
On Fri, Sep 17, 2010 at 2:42 PM, aldus jung wrote:
> We recently upgraded from bind version 9.7.0 to 9.7.1-P2 and we noticed
> that upon start of named, we are
We recently upgraded from bind version 9.7.0 to 9.7.1-P2 and we noticed that
upon start of named, we are seeing the following warning message:
[ID 123 daemon.warning] unable to set effective gid to 0: Not owner
[ID 123 daemon.info] generating session key for dynamic DNS
[ID 123 daemon.warning]
Hi, I am hoping to learn more about how BIND v 9.7.0 implements negative
caching of
delegated subdomains. I've tested and found that BIND observes a different
TTL for
name errors than I would expect it to abide by, but that could be my lack
of understanding of what TTL a DNS server is supposed to
3 matches
Mail list logo