| 18 Dec 2025 |
|  @acidbong:envs.net joined the room. | 07:58:50 |
 K900 | Uhh what | 08:03:52 |
| K900 | What do you even mean by "only allows lookups for a TLD" | 08:04:04 |
|  Dieselgert Baghetto joined the room. | 08:39:11 |
 n4ch723hr3r (putting stuff in your name is cringe) | you define multiple DNS servers in resolved with the option to for example only use 1.1.1.1 for .local domains | 09:39:32 |
| K900 | ...and? | 09:39:45 |
| K900 | It can be any prefix | 09:39:47 |
| K900 | Not just a TLD | 09:39:49 |
| n4ch723hr3r (putting stuff in your name is cringe) | yeah but the dns is just the hostname (which in my case are alphanumeric chars) | 09:56:48 |
| 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 |
