setsocket errors - and a journal file question

Ian Farr

unread,

Jan 4, 2001, 11:26:38 AM1/4/01

to

Hello all,

I have downloaded/compiled/installed bind 9.01, and when I start up named, I
get the following errors:

Jan 04 08:27:39.202 socket.c:1183: unexpected error:
Jan 04 08:27:39.205 setsockopt(10, SO_TIMESTAMP) failed
Jan 04 08:27:39.232 socket.c:1183: unexpected error:
Jan 04 08:27:39.234 setsockopt(9, SO_TIMESTAMP) failed

Any ideas?

Also, I have 2 zones which I want to do dynamic updates on, but, named isn't
creating the journal file - can I manually create one? All named says is the
following:

Jan 04 08:27:39.256 dns_zone_load: zone 0.0.127.in-addr.arpa/IN: start
Jan 04 08:27:39.271 dns_zone_load: zone 0.0.127.in-addr.arpa/IN: loaded
Jan 04 08:27:39.274 dns_zone_load: zone 0.0.127.in-addr.arpa/IN:
dns_journal_rollforward: no journal
Jan 04 08:27:39.276 dns_zone_load: zone 32.26.172.in-addr.arpa/IN: start
Jan 04 08:27:39.292 dns_zone_load: zone 32.26.172.in-addr.arpa/IN: loaded
Jan 04 08:27:39.297 dns_zone_load: zone 32.26.172.in-addr.arpa/IN:
dns_journal_rollforward: no journal
Jan 04 08:27:39.300 dns_zone_load: zone 33.26.172.in-addr.arpa/IN: start
Jan 04 08:27:39.311 dns_zone_load: zone 33.26.172.in-addr.arpa/IN: loaded
Jan 04 08:27:39.316 dns_zone_load: zone 33.26.172.in-addr.arpa/IN:
dns_journal_rollforward: no journal
Jan 04 08:27:39.319 dns_zone_load: zone priv.asherfarr.net/IN: start
Jan 04 08:27:39.335 dns_zone_load: zone priv.asherfarr.net/IN: loaded
Jan 04 08:27:39.337 dns_zone_load: zone priv.asherfarr.net/IN:
dns_journal_rollforward: no journal
Jan 04 08:27:39.340 dns_zone_load: zone dyn.priv.asherfarr.net/IN: start
Jan 04 08:27:39.356 dns_zone_load: zone dyn.priv.asherfarr.net/IN: loaded
Jan 04 08:27:39.358 dns_zone_load: zone dyn.priv.asherfarr.net/IN:
dns_journal_rollforward: no journal
Jan 04 08:27:39.361 dns_zone_maintenance: zone priv.asherfarr.net/IN: enter
Jan 04 08:27:39.364 dns_zone_maintenance: zone dyn.priv.asherfarr.net/IN:
enter
Jan 04 08:27:39.367 dns_zone_maintenance: zone 0.0.127.in-addr.arpa/IN:
enter
Jan 04 08:27:39.369 dns_zone_maintenance: zone 32.26.172.in-addr.arpa/IN:
enter
Jan 04 08:27:39.371 dns_zone_maintenance: zone 33.26.172.in-addr.arpa/IN:
enter
Jan 04 08:27:39.373 dns_zone_maintenance: zone version.bind/CH: enter
Jan 04 08:27:39.375 running

Everything start up, and all static zones are fine, but my dhcpd can not
update the dynamic zone because name can't write it to the .jnl file.

NOTE: I have a backup of my first attempt of installing bind 9.0.0 which has
the journal files, and if I restore these, all is well, but they contain
RR's that are wrong, and I only want to go down that road as a last resort.

Thanks for your help.

Ian Farr

Mark.A...@nominum.com

unread,

Jan 4, 2001, 5:16:34 PM1/4/01

to

>
> Hello all,
>
> I have downloaded/compiled/installed bind 9.01, and when I start up named, I
> get the following errors:
>
> Jan 04 08:27:39.202 socket.c:1183: unexpected error:
> Jan 04 08:27:39.205 setsockopt(10, SO_TIMESTAMP) failed
> Jan 04 08:27:39.232 socket.c:1183: unexpected error:
> Jan 04 08:27:39.234 setsockopt(9, SO_TIMESTAMP) failed
>
> Any ideas?

Ignore these. Your kernel and userland are out of sync.

named gives up most of it privledges including those to write
to arbitary files. Make sure the file permissions are such
that named can write to the files (ad directories) as if root
was a ordinary user.

Mark

>
> NOTE: I have a backup of my first attempt of installing bind 9.0.0 which has
> the journal files, and if I restore these, all is well, but they contain
> RR's that are wrong, and I only want to go down that road as a last resort.
>
> Thanks for your help.
>
> Ian Farr
>
>

--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.A...@nominum.com

Jeffrey C. Albro

unread,

Jan 4, 2001, 6:19:26 PM1/4/01

to

>
> named gives up most of it privledges including those to write
> to arbitary files. Make sure the file permissions are such
> that named can write to the files (ad directories) as if root
> was a ordinary user.
>
> Mark

Um, Huh? I run named as user named, group named on my boxes. It sounds
like you are saying I doesn't need to do that?

-Jeff

Mark.A...@nominum.com

unread,

Jan 4, 2001, 6:33:08 PM1/4/01

to

From the 9.1 FAQ.

Q: Why doesn't -u work on Linux 2.2.x?

A: Linux threads do not fully implement the Posix threads (pthreads) standard.
In particular, setuid() operates only on the current thread, not the full
process. Because of this limitation, BIND 9 cannot use setuid() on Linux as it
can on all other supported platforms. setuid() cannot be called before
creating threads, since the server does not start listening on reserved ports
until after threads have started.

In the 2.3.99-pre3 and newer kernels, the ability to preserve capabilities
across a setuid() call is present. This allows BIND 9 to call setuid() early,
while retaining the ability to bind reserved ports. This is a Linux-specific
hack.

On a 2.2 kernel, BIND 9 does drop many root privileges, so it should be less
of a security risk than a root process that has not dropped privileges.

If Linux threads ever work correctly, this restriction will go away.

Configuring BIND9 with the --disable-threads option causes a non-threaded
version to be built, which will allow -u to be used.

Jeffrey C. Albro

unread,

Jan 4, 2001, 10:44:15 PM1/4/01

to

Ohhhhhh : ) I was talking about 8.2.2p7... It looks like you are talking
about 9.1. I am running bind 8.2.2p7 as named -u named -g named

-Jeff

Mark.A...@nominum.com

unread,

Jan 4, 2001, 10:53:55 PM1/4/01

to

>
>
>
> Ohhhhhh : ) I was talking about 8.2.2p7... It looks like you are talking
> about 9.1. I am running bind 8.2.2p7 as named -u named -g named
>
> -Jeff

The initial question was about BIND 9. This was implied by the
error messages.

Mark