-
### What is the issue?
When you enable MagicDNS in the DNS settings, name resolution stops working on Android completely. Internal DNS names within the tailnet are resolved successfully by any other …
-
Alpine get SERVFAIL on nslookup. For example I can replicate using nameserver 195.238.40.45.
Tested on ubuntu and macos and it works fine.
To replicate
`docker run -it alpine /bin/sh`
…
-
- https://vercel.com/spencerlepines-projects/portfolio/settings/domains
- https://aws.amazon.com/
-
### Search first
- [X] I searched and no similar issues were found
### What Happened?
This problem exists on Windows. Some nodes cannot be connected using VPN mode, but Windows has 4 proxy modes. I…
-
Current draft mentions that DNS-SD does not allow an empty TXT record
> A variation may have the option of being represented by the empty string "". This is not allowed in the DNS-SD encoding, and…
-
# Scenario
A Ministry team requests a customization or exception to their Project Set. In this scenario, a team is trying to use Confluent Cloud, and requires Private Endpoints, a Private DNS Zone, a…
-
### Description:
In our environment, DNS resolution over UDP is blocked, so we've configured pods to use TCP for DNS resolution instead. Testing with ping confirms that DNS resolution over TCP work…
-
Hello,
I've an issue with the DNS protocol.
On my lab I've a workstation (192.168.128.2), a bind DNS server (internal IP 192.168.128.10, external IP 185.217.171.10) and the Sliver server (185.217.…
-
I have these parameters:
And only the wireguard protocol uses them. For example, a couple of lines from the…
-
### The purpose and use-cases of the new component
The DNS lookup Processor is for resolving hostnames to IP addresses and vice versa. It is particularly useful when the GeoIP processor receives a …