Re: flushing an errant resolver

2010-11-26 Thread David Newman
On 11/25/10 2:47 PM, Stuart Henderson wrote: > Postfix - the network daemons are most likely chroot'ed to > /var/spool/postfix and there will be an etc/resolv.conf in the > jail. Bingo. It's coming up on 17 hours since changing this and restarting postfix. So far there haven't been any more querie

Re: flushing an errant resolver

2010-11-25 Thread Stuart Henderson
On 2010-11-25, David Newman wrote: > Greetings. I manage an mail server running OpenBSD 4.5 i386. For various > layer-9 reasons I cannot reboot the server at this time let alone > upgrade it. I can stop and restart processes. > > Awhile back when changing ISPs I temporarily added Google's public >

Re: flushing an errant resolver

2010-11-25 Thread Ted Unangst
The libc resolver automatically picks up changes in resolv.conf. If that's not happening, you have a server that uses its own resolver. netstart and other network configuration has nothing to do with it, btw. On Nov 25, 2010, at 1:31 PM, David Newman wrote: > Greetings. I manage an mail server

flushing an errant resolver

2010-11-25 Thread David Newman
Greetings. I manage an mail server running OpenBSD 4.5 i386. For various layer-9 reasons I cannot reboot the server at this time let alone upgrade it. I can stop and restart processes. Awhile back when changing ISPs I temporarily added Google's public nameserver at 8.8.8.8 to /etc/resolv.conf. Alt