Miles Fidelman wrote:
Perhaps a silly thought, but home routers are usually configured to
access an external nameserver not one on the local network. Perhaps
it can't reach the nameserver.
I was thinking the same thing.
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.
Regards
--
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/4c4d8fa7.60...@gmail.com
