Skip to content
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

Open
rgfhfdghfgdh435645365 opened this issue Sep 18, 2019 · 12 comments
Open

Should resolve Internal DNS [Fail] #60

rgfhfdghfgdh435645365 opened this issue Sep 18, 2019 · 12 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@rgfhfdghfgdh435645365
Copy link

        [t][domain.local][server.domain.local] Should resolve Internal DNS [Fail] [Cannot process argument transformation on parameter 'ExtendedValue'. Cannot convert value to type System.String.]

if dup, close. if issue with my dns, please let me know where to look.

PrzemyslawKlys added a commit that referenced this issue Sep 18, 2019
@PrzemyslawKlys
Copy link
Member

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.

@PrzemyslawKlys PrzemyslawKlys added the bug Something isn't working label Sep 18, 2019
@rgfhfdghfgdh435645365
Copy link
Author

the second ip is just the wireshark loopback

@PrzemyslawKlys
Copy link
Member

Even more, it should be removed, or at least configured properly.

PS C:\Support\GitHub\Testimo> Resolve-DnsName -Name 'ad1.ad.evotec.xyz'

Name                                           Type   TTL   Section    IPAddress
----                                           ----   ---   -------    ---------
ad1.ad.evotec.xyz                              A      3600  Answer     192.168.240.189

Your DNS server when asked about your DC is returning two IP's. One "proper", the other one... loopback.

@rgfhfdghfgdh435645365
Copy link
Author

its configured however wireshark wanted it configured when I installed wireshark.

its disabled until I need it anyway.

@PrzemyslawKlys
Copy link
Member

It's still in DNS thou. You need to fix that.

@rgfhfdghfgdh435645365
Copy link
Author

its not though...

@PrzemyslawKlys
Copy link
Member

Resolve-DnsName -Name 'yourdc'

What does this return? 1 IP or more?

@rgfhfdghfgdh435645365
Copy link
Author

an ipv4 and ipv6 ip address that is not the wireshark loopback.

@PrzemyslawKlys
Copy link
Member

ok, so it's IPV6. That's another thing I need to consider. Thanks!

@PrzemyslawKlys PrzemyslawKlys added the enhancement New feature or request label Sep 18, 2019
@PrzemyslawKlys
Copy link
Member

So the bug is fixed, however, I will have to work on the test to skip IPV6 on this test.

@rafalfitt
Copy link

please treat IPv6 as important as IPv4. Do not skip IPv6.

@PrzemyslawKlys
Copy link
Member

Will do, no worries. Just not much testing ground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants