This message was deleted.
# general
a
This message was deleted.
h
how did you expose that port? and is it TCP or UDP ?
kubectl get svc
d
both
there
h
so from a remote machine if you do:
nc -v 192.168.3.212 53
what happens?
remote machine that is not part of this cluster
d
yes
there
and it hangs
h
typically if its working it should show "connected... " now if you run the same command from one of the cluster node what happens
d
checking...
h
nslookup <http://rancher.com|rancher.com> 192.168.3.212
so that's where the issue is do you have metallb or is this in cloud ? or something else ?
d
Yes metallb
I install a simple nginx the same way I did bind9 and if I do curl from any in the cluster or not I'm able to see the website
so I really confuse of what's the problem 😞
BTW here is for the testing nginx
the same, hang
Question: have something to do that is running on namespace and not in default?
Can you please explains me what the issue is?
h
does not matter if its in default or not (unless your cluster has some policy that does not allow)
d
I don't think so
thanks! for that answer.
So what do you think it's the problem?
h
what are you using for loadbalancer service? is this on-prim or in cloud ?
d
I'm using metallb
on-prim
h
okay so if HTTP service is working then confirm if you can do nslookup from cluster node if that works then check network firewall settings to see if that is the issue
d
I'm looking my mind here I really don't have a clue why this is not working
I have tried different images of bind9 and they all do the same thing
show the external IP but I'm unable to get it to work
if I do nmap -PS bla.bla.lbla.bla where this is the external IP of the dns sever
it will return host down
if I do the same on the Ngnix it will list me the 80 port open
why?
what I missing for it to work