| 18 Dec 2025 |
 n4ch723hr3r (putting stuff in your name is cringe) | so the dns does NOT work with something like dig myhost.local @myserver. instead you have to do dig myhost @myserver | 09:57:53 |
 K900 | You should use a separate domain name (possibly under arpa.home if you don't have a public one) and then set the search domain instead | 09:58:08 |
| K900 | So the canonical names for your hosts are foo.n4ch723hr3r.home.arpa or whatever | 09:58:36 |
| n4ch723hr3r (putting stuff in your name is cringe) | yes but the nebula DNS server does not have the functionality for that | 09:58:38 |
| K900 | And your search domain is n4ch723hr3r.home.arpa | 09:58:42 |
 magic_rb | Thats a nebula bug then | 09:59:03 |
| n4ch723hr3r (putting stuff in your name is cringe) | i need a reverse proxy but for DNS | 09:59:05 |
| n4ch723hr3r (putting stuff in your name is cringe) | its experimental | 09:59:11 |
| magic_rb | You need to put your local dns under a tld | 09:59:18 |
| n4ch723hr3r (putting stuff in your name is cringe) | how? | 09:59:27 |
| magic_rb | By fixing the nebula dns server | 09:59:36 |
| magic_rb | How would a rproxy help? | 09:59:43 |
| n4ch723hr3r (putting stuff in your name is cringe) | i cant do that. nebula DNS doesnt have that feature | 10:00:10 |
| n4ch723hr3r (putting stuff in your name is cringe) | https://nebula.defined.net/docs/guides/using-lighthouse-dns/ | 10:00:12 |
| K900 | I think they want a rewriting DNS resolver that will automagically rewrite foo.n4ch723hr3r.home.arpa or whatever to just foo and then forward that to the Nebula nameserver | 10:00:15 |
| K900 | But that's horrible | 10:00:16 |
