Having to connect twice to another vlan from main LAN

[mkono87]

I have a single VLAN that is excluded from my main LAN but I have aliases set up to allow connection from my computer to that vlan. For what its worth, I have the adguard home port installed and in use for my dns filtering. I have unbound still enabled on port 5353. In unbound I have checked register dhcp leases and static mappings.

LAN - 192.168.10.1
VLAN - 192.168.30.1

The thing I have noticed that when I try to connect to the VLAN even by a simple ping or to access a web ui. It will hang on a first attempt. If I cancel and ping again or refresh the page it connects without issue. Im not exactly where this is happening. Its acting is if there is no route table created or something. I also cannot contact using the hostnames. Within LAN there doesnt seem to be an issue with hostnames or connecting first try.

Would love some insight into why this could be happening. Forgive me if this isnt enough info, just ask and il be happy to provide.

[mkono87]

I also noticed that when I ping my vlan for some reason I get a response from a random ip that used to be a vm. Not sure why the heck thats showing, it had nothing to do with DNS.

Ping from 192.168.10.15

Pinging 192.168.30.4 with 32 bytes of data:
Reply from 192.168.30.7: Destination host unreachable.
Request timed out.