Move todo items to issue: #77

docs/guides/using-lighthouse-dns/index.mdx

@@ -112,27 +112,3 @@ import { ValidateDomainInput } from './ValidateDomainInput';
 - Can the lighthouse resolve its own name?
   - As of nebula `v1.6.1`, no, the lighthouse only responds about hosts it has handshaked with, it never handshakes with
     itself. [slackhq/nebula/issues/560](https://github.com/slackhq/nebula/issues/560) is tracking this feature.
-
-## TODO
-
-Document Windows DNS setup?
-
-> If it does work then
->
-> `Add-DnsClientNrptRule -Namespace ".<domain>" -NameServers "<lighthouse ip>"` using powershell will tell windows to
-> include your lighthouse dns server in name lookups.
->
-> This means that your nebula hosts will need to share a domain name. You may be able to omit the -Namespace option but
-> I didn't try it.
->
-> https://github.com/slackhq/nebula/issues/110#issuecomment-578470077
-
-Explain how to set up groups for firewall rules?
-
-Document how to set up DNS consumption w/ `dnsmasq` on Ubuntu?
-
-see <https://github.com/DefinedNet/nebula-docs/pull/68#issuecomment-1343201269> and these slackhq/nebula issues:
-
-- https://github.com/slackhq/nebula/issues/434
-- https://github.com/slackhq/nebula/issues/110
-- https://github.com/slackhq/nebula/issues/175