Re: access rdomain0 localhost from rdomainN

2023-06-28 Thread Stuart Henderson
On 2023/06/28 10:37, Zack Newman wrote: > On 2023-05-15, Stuart Henderson wrote: > > pass out quick on rdomain 2 to 127.0.0.1 nat-to 127.0.0.1 rtable 0 > > Not sure what the proper etiquette is here-in particular if I should > start a new thread seeing how this reply is over a month late-so feel

Re: access rdomain0 localhost from rdomainN

2023-06-28 Thread Zack Newman
On 2023-05-15, Stuart Henderson wrote: pass out quick on rdomain 2 to 127.0.0.1 nat-to 127.0.0.1 rtable 0 Not sure what the proper etiquette is here-in particular if I should start a new thread seeing how this reply is over a month late-so feel free to yell at me. What is the purpose of the "

Re: access rdomain0 localhost from rdomainN

2023-05-15 Thread Joel Carnat
On Mon, May 15, 2023 at 10:21:55AM -, Stuart Henderson wrote: > > I think your options are 1) run a second copy (I suggest symlinking > rc.d/unbound -> e.g. rc.d/unbound1, and setting unbound1_rtable=1), > or 2) leak the traffic between tables using a PF rule, I have this > on my laptop: > >

Re: access rdomain0 localhost from rdomainN

2023-05-15 Thread Stuart Henderson
On 2023-05-15, Joel Carnat wrote: > On Sun, May 14, 2023 at 10:32:15PM -0600, Zack Newman wrote: >> On 2023-05-14, Joel Carnat wrote: >> > I have unbound listening on lo0 (127.0.0.1, rdomain0) and resolv.conf >> > configured with "nameserver 127.0.0.1". >> >> You can also have unbound(8) listen

Re: access rdomain0 localhost from rdomainN

2023-05-15 Thread Joel Carnat
On Sun, May 14, 2023 at 10:32:15PM -0600, Zack Newman wrote: > On 2023-05-14, Joel Carnat wrote: > > I have unbound listening on lo0 (127.0.0.1, rdomain0) and resolv.conf > > configured with "nameserver 127.0.0.1". > > You can also have unbound(8) listen on lo1. > I have tried that but this see

Re: access rdomain0 localhost from rdomainN

2023-05-14 Thread Zack Newman
On 2023-05-14, Joel Carnat wrote: I have unbound listening on lo0 (127.0.0.1, rdomain0) and resolv.conf configured with "nameserver 127.0.0.1". You can also have unbound(8) listen on lo1. Without more information-for example, showing what pf.conf(5) contains- there is no way we can help you.

access rdomain0 localhost from rdomainN

2023-05-14 Thread Joel Carnat
Hi, I have configured rdomain 1 and bound daemons (httpd and relayd) to it. They work as expected but I still have issues with DNS resolving on localhost. I have unbound listening on lo0 (127.0.0.1, rdomain0) and resolv.conf configured with "nameserver 127.0.0.1". When I try to use it from