Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
b
busy-judge-4614
03/24/2023, 9:07 PMwhen setting up a service and ingress, how is a host on the local network/lan (same network as cluster) supposed to resolve something like http://media.192.168.1.81.nip.io/ ?
How is my network dns supposed to resolve these? Do I point the nip.io domain at the cluster?
Screenshot 2023-03-24 at 21.14.17.jpg
Screenshot 2023-03-24 at 21.14.45.jpg,Screenshot 2023-03-24 at 21.15.18.jpg
c
creamy-pencil-82913
03/24/2023, 9:22 PMyou don’t point it at anything. the IP address is right there in the hostname
go to https://nip.io/ and read about what it is actually doing for you
nip.io mapsin “dot”, “dash” or “hexadecimal” notation to the corresponding<anything>[.-]<IP Address>.<http://nip.io|nip.io>:<IP Address>
b
busy-judge-4614
03/24/2023, 9:23 PMahh ok
I assumed as I got this error it had some dns issues but as you say, I probably need to read more about nip.io
c
creamy-pencil-82913
03/24/2023, 9:25 PMIt’s hard to know what “cant find the server” means. that address definitely resolves to the correct IP, but perhaps Safari means that it can’t connect to it?
I would test with curl or something else less likely to hide the actual error message from you
b
busy-judge-4614
03/24/2023, 9:30 PMok, so my router is on 192.168.1.1 and I can access it at http://192.168.1.1 so are you saying I should be able to reach it internally at http://192.168.1.1.nip.io ?
[mike@k1 /]$ curl <http://192.168.1.1.nip.io>I am guessing my internal firewall and DNS, which is OPNsense is blocking this
I can look in to that next 🙂
c
creamy-pencil-82913
03/24/2023, 9:37 PMdo you maybe have a pihole or something that’s blocking it?
b
busy-judge-4614
03/24/2023, 9:38 PMno, i beleive my firewall is using something called Unbind DNS
maybe thats blocking it or such
Ok, that fixed it, if I set a dns forward for nip.io to google dns 🙂
wow, what a crazy work around