On 01/05/2021 04:32, Jack Craig wrote:
almost, but no seegar,...
i and continuing to have dig lookups for
linuxlighthouse.com
<
http://linuxlighthouse.com> a is timing out(refused or servfail)
anyone see my misconfiguration??
one error i need to address, my domain is 'linuxlighthouse.com
<
http://linuxlighthouse.com>'
i have mistakenly tried to include
ws.linuxlighthouse.com
<
http://ws.linuxlighthouse.com> &
www.linuxlighthouse.com
<
http://www.linuxlighthouse.com> in my certificates..
i am missing the record to define
www.<linuxlighthouse.com
<
http://linuxlighthouse.com>> ?
I think my last response didn't go far enough to explain.
I had said:
[egreshko@meimei ~]$ host
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> 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; };
meaning only request sent via 127.0.0.1 will be serviced. All other sources will be
REFUSED.
Even a query from another host on your internal 10.0.0.X network will get REFUSED.
You need to fix that configuration option to allow queries from elsewhere.
--
Remind me to ignore comments which aren't germane to the thread.