-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should resolve Internal DNS [Fail] #60
Comments
The issue is on my side. However, it seems like your Domain Controller has 2 IP addresses (or at least that's a guess based on the error. As far as I know, it's best practice to keep only 1 network interface/1 ip per DC. |
the second ip is just the wireshark loopback |
Even more, it should be removed, or at least configured properly.
Your DNS server when asked about your DC is returning two IP's. One "proper", the other one... loopback. |
its configured however wireshark wanted it configured when I installed wireshark. its disabled until I need it anyway. |
It's still in DNS thou. You need to fix that. |
its not though... |
Resolve-DnsName -Name 'yourdc' What does this return? 1 IP or more? |
an ipv4 and ipv6 ip address that is not the wireshark loopback. |
ok, so it's IPV6. That's another thing I need to consider. Thanks! |
So the bug is fixed, however, I will have to work on the test to skip IPV6 on this test. |
please treat IPv6 as important as IPv4. Do not skip IPv6. |
Will do, no worries. Just not much testing ground. |
if dup, close. if issue with my dns, please let me know where to look.
The text was updated successfully, but these errors were encountered: