How to access OKD console once the deployment is complete?

[Gl1TcH_1n_Th3_M4tR1x]

After a successful deployment (based on the quay image:

podman run --rm -it     -v ~/.ssh/id_rsa:/root/.ssh/id_rsa:z   \ 
           -v ~/.ssh/id_rsa.pub:/root/.ssh/id_rsa.pub:z   \  
           -v ~/.ssh/config:/root/.ssh/config:z     \ 
           quay.io/kubeinit/kubeinit:$TAG        \
            -vvv --user root        \ 
            -e kubeinit_spec=okd-libvirt-1-3-1        \ 
            -i ./kubeinit/inventory       \  
            ./kubeinit/playbook.yml

TASK [kubeinit.kubeinit.kubeinit_prepare : End play] ********************************************************************************************************
task path: /root/.ansible/collections/ansible_collections/kubeinit/kubeinit/roles/kubeinit_prepare/tasks/post_deployment.yml:54
META:
skipping: [localhost] => {
   "msg": "",
   "skip_reason": "end_play conditional evaluated to False, continuing play"
}
META: role_complete for localhost
META: ran handlers
META: ran handlers

PLAY RECAP **************************************************************************************************************************************************
hypervisor-01              : ok=17   changed=8    unreachable=0    failed=0    skipped=8    rescued=0    ignored=0
hypervisor-02              : ok=0    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
localhost                  : ok=497  changed=252  unreachable=0    failed=0    skipped=175  rescued=0    ignored=0

and adding to /etc/resolv.conf

# Generated by NetworkManager
search kubeinit.local
nameserver 192.168.0.10

search corp.ads
nameserver 192.168.0.1

my nyctea Hypervisor has IP: 192.168.0.10

I can't access the console:

dig console-openshift-console.apps.okdcluster.kubeinit.local

; <<>> DiG 9.11.36-RedHat-9.11.36-2.el8 <<>> console-openshift-console.apps.okdcluster.kubeinit.local
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51943
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;console-openshift-console.apps.okdcluster.kubeinit.local. IN A

;; Query time: 1 msec
;; SERVER: 192.168.122.1#53(192.168.122.1)
;; WHEN: Fri Feb 25 14:03:31 EST 2022
;; MSG SIZE  rcvd: 85

I also need to know how to configure a Windows 10 machine to be able to open the console from there.

[Gl1TcH_1n_Th3_M4tR1x]

I just changed my DNS server to be 10.0.0.253 for the kubeinit.local domain and now I can access the console:
Here my new /etc/resolv.conf

# Generated by NetworkManager
search kubeinit.local
nameserver 10.0.0.100

search corp.ads
nameserver 192.168.0.1