Dear folks,
I am unable to
dig humaaraartha.in @103.236.115.116
from outside. From the host itself,
dig humaaraartha.in @localhost
works.
You can browse the website at http://103.236.115.116
Kindly cc me as I am not subscribed.
Thanking you
Sagar Acharya
Dear folks,
I am unable to
dig humaaraartha.in @103.236.115.116
from outside. From the host itself,
dig humaaraartha.in @localhost
works.
You can browse the website at http://103.236.115.116
Kindly cc me as I am not subscribed.
Thanking you
Sagar Acharya
Hi Sagar,
It's hard to say what the problem is without knowing the type of error,
but since it works from localhost, I'm assuming NSD successfully loads
the zone etc.
If you've not specified any address, by default NSD listens on all
interfaces. In that case chances are the firewall is blocking traffic.
It may also be that NSD is not listening on the specified address, in
that case please add the proper "ip-address" option to nsd.conf.
Best regards,
Jeroen Koekkoek
Tried with ip-address option, it is not working.
I think ip-address binds to local ip address. Anyways localhost binds to the same ip as that of http, 0.0.0.0 , so everything is right from the system.
How do I test udp from other network as dig tests over udp. Or can I dig over tcp?
Thanking you
Sagar Acharya
P.S. @Anand, chup hojaa. Bhauk mat.
Have you bothered reading the man page of dig with "man dig"? If you had, you'd know whether you can use tcp or not.
But you just want to be spoon-fed answers. That's a rather lazy attitude.
Tried with ip-address option, it is not working.
I think ip-address binds to local ip address. Anyways localhost binds to the same ip as that of
http, 0.0.0.0 , so everything is right from the system.
If your host has multiple addresses, binding to 0.0.0.0 will often
not do what you want for UDP. The source address of responses will
not necessarily be the same address as the query was sent to.
This is also described in the nsd.conf(5) manual in the description
of the "ip-address" option.
I suggest listing the specific IP addresses on which NSD will be
sent DNS queries.
Also use e.g. tcpdump to check that the queries are actually received
at your machine and not filtered upstream.
How do I test udp from other network as dig tests over udp. Or can I dig over tcp?
"dig +tcp" will use TCP for the test, but TCP does not have the above
problem on multi-homed hosts.
I have eth0 and using pppd, a sort of virtual node ppp0 is generated, I believe that something is going wrong in the sense, by default, nsd is going to eth0 when it should go to ppp0.
Can that be the issue?
Would I have to add some routing rules there?
Adding ip-address lines for both addresses might fix it.
With
dig humaaraartha.in @103.236.115.116 +tcp
I am able to get a response but
dig humaaraartha.in @103.236.115.116
doesn’t return anything. There seems to be a problem with udp!
The response is lost! If you can replicate this, kindly confirm!
Thanking you
Sagar Acharya