Christopher H's questions

I'm having issues with 2 VyOS routers, not being able to ping IP address on VIF interfaces. Below is the configuration on the router, which is also running BGP (which I've confirmed is working as expected).

high-availability {
    vrrp {
        group VL200 {
            hello-source-address 203.0.113.28
            interface eth1.200
            no-preempt
            peer-address 203.0.113.29
            priority 200
            virtual-address 203.0.113.30/27
            vrid 20
        }
    }
}
interfaces {
    ethernet eth0 {
        hw-id nn:nn:nn:nn:nn:nn
        vif 65 {
            address 192.0.2.1/29
        }
    }
    ethernet eth1 {
        address 203.0.113.111/32
        hw-id nn:nn:nn:nn:nn:nn
        vif 100 {
            address 10.20.0.252/24
        }
        vif 200 {
            address 203.0.113.28/27
        }
    }
    loopback lo {
        address 203.0.113.222/32
    }
}
protocols {
    bgp 64511 {
        address-family {
            ipv4-unicast {
                network 203.0.113.0/24 {
                }
            }
        }
        neighbor 192.0.2.6 {
            ebgp-multihop 2
            remote-as 64496
            update-source 192.0.2.1
        }
        parameters {
            router-id 192.0.2.1
        }
    }
    static {
        route 0.0.0.0/0 {
            next-hop 192.0.2.6 {
                distance 253
            }
        }
        route 203.0.113.0/24 {
            blackhole {
                distance 254
            }
        }
    }
}

From an external computer, I am able to ping 203.0.113.111 and 203.0.113.222, however I cannot ping 203.0.113.28 or 203.0.113.30. My config does not appear to be missing anything that I know of.

I look after a Windows network which has two Hyper-V servers in a failover cluster using DAS, accessible by both hosts with two DCs (both on WS2019, one on each host). We have been having issues with our SDC running on the second host where it was giving us the below error:

The security database on the server does not have a computer account for this workstation trust relationship.

I live-migrated the VM to our first host and rebooted it, and it appears to have resolved the issue. It was moved back to the second VM host and has been happy ever since.

We now have (I believe) another issue that has manifested. For some reason, whenever I run the command "netdom verify dc1" on either DC, we get the following error:

The specified domain either does not exist or could not be contacted.

The command failed to complete successfully.

However when I run the command "netdom verify dc2" it is successful and returns the below:

The secure channel from DC2 to the domain ADSROOT has been verified. The connection is with the machine \\DC1.example.com

The command completed successfully.

Is it normal for a DC to return a failure for a PDC, and a success for a SDC? I would think not. Any ideas?