Re: bind9 problems
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Am 26.07.10 15:17, schrieb Miles Fidelman:
> Panayiotis Karabassis wrote:
>> The DNS server seems to be working fine when accessed directly (i.e.
>> through nslookup or by setting it as the primary nameserver for the
>> computer manually throught /etc/resolv.conf).
>
> 1. see if you can traceroute the nameserver from somewhere off your
> local network (make sure to traceroute to port 53)
>
> 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)
>
> Miles Fidelman
>
This only applies if he wants have a public DNS. And that only would
make sense if he wants manage his own domain. If he only wants resolv in
the local LAN, he should NOT open port 53 inbound.
as he stated in his first mail, his server CAN resolve things if asked
directly. Just chaining trough the router fails. Therefore, this is not
a router firewall problem (it may be a server firewall problem).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iF4EAREIAAYFAkxNrJEACgkQpjmLjrU66/5dRAEAguowQNp5IXWagMHTPi/zYdiz
2oBtxU2Cwv4FzPsMy/MA/2N9COQkvuBRiJ9oH8+rtHdTBcfAUcbT+1pCoFnVzkP9
=ZTU4
-----END PGP SIGNATURE-----
Reply to: