Re: problem running named in non 0 rdomain

2012-01-03 Thread Pete Vickers
On 1. jan. 2012, at 23.40, Stuart Henderson wrote: > On 2012-01-01, Pete Vickers wrote: >> snippet from /etc/named-gn.conf : >> controls { >> inet 10.20.30.2 port 954 allow {10.20.30.2;} keys {"rndc-key";}; >> }; >> >> then it also fails and complains thus: >> >> Jan 1 09:01:49 ns0 named[8504]

Re: problem running named in non 0 rdomain

2012-01-03 Thread Russell Garrison
On Sun, Jan 1, 2012 at 5:40 PM, Stuart Henderson wrote: > I'm pretty sure the child will be inheriting the rdomain from the process > which forked it. > I can offer the anecdote that when I ran sshd using the route -exec wrapper my child session would exist in whatever rdomain was hosting the da

Re: problem running named in non 0 rdomain

2012-01-01 Thread Stuart Henderson
On 2012-01-01, Pete Vickers wrote: > snippet from /etc/named-gn.conf : > controls { >inet 10.20.30.2 port 954 allow {10.20.30.2;} keys {"rndc-key";}; > }; > > then it also fails and complains thus: > > Jan 1 09:01:49 ns0 named[8504]: [child]: disallowed port 954 > Jan 1 09:01:49 ns0 named[85

problem running named in non 0 rdomain

2012-01-01 Thread Pete Vickers
Hi, I am having difficulty running named in a non-default rdomain, on the following platform: root@ns0 ~ # uname -a OpenBSD ns0.whatever 5.0 GENERIC#36 sparc64 I have an interface in a rdomain '1': root@ns0 ~ # ifconfig bge1 | head -1 bge1: flags=28843 rdomain 1 mtu 1500 and happy: root@ns0