Should resolve Internal DNS [Fail]

EvotecIT / Testimo

Testimo is a PowerShell module for running health checks for Active Directory against a bunch of different tests

547 stars 58 forks source link

Should resolve Internal DNS [Fail] #60

Open rgfhfdghfgdh435645365 opened 5 years ago

rgfhfdghfgdh435645365 commented 5 years ago

        [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 commented 5 years ago

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.

rgfhfdghfgdh435645365 commented 5 years ago

the second ip is just the wireshark loopback

PrzemyslawKlys commented 5 years ago

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 commented 5 years ago

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

its disabled until I need it anyway.

PrzemyslawKlys commented 5 years ago

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

rgfhfdghfgdh435645365 commented 5 years ago

its not though...

PrzemyslawKlys commented 5 years ago

Resolve-DnsName -Name 'yourdc'

What does this return? 1 IP or more?

rgfhfdghfgdh435645365 commented 5 years ago

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

PrzemyslawKlys commented 5 years ago

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

PrzemyslawKlys commented 5 years ago

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

rafalfitt commented 5 years ago

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

PrzemyslawKlys commented 5 years ago

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