Re: on to letsencrypt

[Ed Greshko]

On 01/05/2021 11:28, Jack Craig wrote:
> On Fri, Apr 30, 2021 at 3:03 PM Ed Greshko <[e-mail] > wrote:
> >
> >
> >     [egreshko@meimei ~]$ host cnn.com <http://cnn.com> <http://cnn.com <http://cnn.com>> 108.220.213.121
> >     Using domain server:
> >     Name: 108.220.213.121
> >     Address: 108.220.213.121#53
> >     Aliases:
> >
> >     Host cnn.com <http://cnn.com> <http://cnn.com <http://cnn.com>> not found: 5(REFUSED)
> >
> >     Which is correct since your named.conf currently contains
> >
> >              allow-query     { localhost; };
> >
> >     So, at least your server is now contactable from the Internet.  So you can go about adding in the zones
> >     you need as well as the access you want to allow.
> >
>
> Your dns server REFUSED to answer the query.  That is "correct" for the *test* named.conf file I sent.
> The *test* configuration contains....
>
> allow-query     { localhost; };
>
>
> i would think that *allow-query { localhost; 108.220.213.121; };*
>
> but that does not appear to work for me. what am i missing here?

You are missing the fact that you attempting to run a *public* DNS server.

That means that your DNS server must accept queries from *any* source address.

allow-query     { any; };

is what you'll need.