On 01/05/2021 12:31, Jack Craig wrote:
>
>
> On Fri, Apr 30, 2021 at 9:05 PM Ed Greshko <ed.greshko@greshko.com <mailto:ed.greshko@greshko.com>> wrote:
>
> On 01/05/2021 11:46, Jack Craig wrote:
> > adding 108.220.213.121 to /etc/resolv.conf also doesnt seem to help...
>
> That file has nothing to do with the DNS server.
>
>
> I thought that list of NSs was the NS list used to resolve any lookup, yet another misconception on my part...
>
> as allow-query { any; };
>
> alone does not clear up the dns lookup failure, i had an earlier zone file that spelled out my noton of domain lookup,
> what is the lookup process laid out?
>
> *REFUSED unexpected RCODE resolving 'linuxlighthouse.com/A/IN <http://linuxlighthouse.com/A/IN>': 144.160.20.47#53*
> what is more i find the below error in the named-run log, how do i drill down to find this ns3.attdns
> lookup failure??
>
You're sort of getting there. Right now you have recursion turn on. Eventually you'll want to turn
that off.
But, at the moment if query your server I get
[egreshko@acer ~]$ host cnn.com 108.220.213.121
Using domain server:
Name: 108.220.213.121
Address: 108.220.213.121#53
Aliases:
cnn.com has address 151.101.1.67
etc.....
Which means at least it is listening and processing recursive queries.
However.....
[egreshko@acer ~]$ host ws.linuxlighthouse.com 108.220.213.121
;; connection timed out; no servers could be reached
That would seem to suggest that you don't have a zone configured for linuxlighthouse.com.
seems t be working better, how many holes do you see at this point??
thx, ...