Aaron,
Listening to 127.0.0.1 and not on the other addresses would make this work
on port 80 on localhost only. That's just how the TCP stack works. If you
want to test this, find whatever your DHCP IP address is (`ifconfig en0`)
and listen on that IP address. You should find that you can hit p
Mikkel,
Cheers ! Knew it had to be sometyhing simple. Stange that port 80 works
with localhost 127.0.0.1 though ?
Aaron
On 10 August 2017 at 19:37, Mikkel Wilson wrote:
> I haven't run this locally to test, but you appear to be binding only to
> the localhost address: https://github.com/tjfont
I haven't run this locally to test, but you appear to be binding only to
the localhost
address:
https://github.com/tjfontaine/node-dns/blob/master/examples/forwarder.js#L10
This should exhibit the symptoms you mention and allow it to work on
localhost and not on remote addresses. Change this f
On 08/06/2017 10:42 AM, Aaron Gray wrote:
> Hi,
>
> I have a node.js based dns program on port 53 and have it working as
> localhost on debian 8.5 but I cannot seem to get it to work externally
> despite getting the firewall rules right having tested them with Bind9.
Check if it's listening on lo
Hi,
I have a node.js based dns program on port 53 and have it working as
localhost on debian 8.5 but I cannot seem to get it to work externally
despite getting the firewall rules right having tested them with Bind9.
-A INPUT -p udp --dport 53 --sport 1024:65535 -j ACCEPT
-A OUTPUT -p udp --sport
5 matches
Mail list logo
