Panayiotis Karabassis wrote:
Two thoughts come to mind:
1. see if you can traceroute the nameserver from somewhere off your
local network (make sure to traceroute to port 53)
The nameserver is not visible to the external world. Should I forward
the port?
2. look at your router config - see if its blocking port 53 - if so,
try unblocking it (note that this will open your nameserver to the
world - so you'd need to lock that down a bit)
I don't think it is blocking it.
These two statements are contradictory. If the nameserver is not
visible to the external world, then its precisely because your router is
blocking the port. Try forwarding the port and see what happens. If it
works, then you should immediately figure out how to lock things down so
only your local machines can access the port.
--
In theory, there is no difference between theory and practice.
In<fnord> practice, there is. .... Yogi Berra
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c4d9555.8090...@meetinghouse.net
