crc: [BUG] Unable to connect to CRC remotely on F33 with systemd-resolved.

Regarding: https://code-ready.github.io/crc/#connecting-to-remote-instance_gsg

Is it possible to set this up on F33 using systemd-resolved?

I have to managed to create a dummy interface

sudo ip link add type dummy crc
sudo ip link set dummy0 name crc
sudo ip link set crc up

and assign the following to it

sudo resolvectl domain crc '~crc.testing'
sudo resolvectl dns crc 192.168.0.70
resolvectl status crc                                                                                                                                    ✔  4m 15s  66  
Link 21 (crc)
Current Scopes: none                                                        
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
   DNS Servers: 192.168.0.70                                                
    DNS Domain: ~crc.testing

However, I am still unable to resolve crc.testing to my server on my home network.

About this issue

Original URL
State: open
Created 3 years ago
Comments: 18 (15 by maintainers)

Most upvoted comments

$ cat /etc/systemd/resolved.conf.d/crc.conf                                                                                                                                                
[Resolve]
DNS=127.0.0.1
Domains=~apps-crc.testing ~crc.testing
$ cat /etc/systemd/resolved.conf                                                                                                                                                                
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
#FallbackDNS=
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes

dofinn on Feb 19, 2021

So i would be in favour of documenting https://github.com/code-ready/crc/issues/1954#issuecomment-773813647 for F33 only. This sends traffic only destined for the crc.testing domain to your remote machine that hosts CRC.

The complete solution is those configurations + sudo systemctl enable --now dnsmasq

dofinn on Feb 9, 2021