Re: on to letsencrypt

[Jack Craig]

On Fri, Apr 30, 2021 at 10:14 PM Ed Greshko  wrote:
> On 01/05/2021 12:31, Jack Craig wrote:
> > On Fri, Apr 30, 2021 at 9:05 PM Ed Greshko <[e-mail]
>
> > 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%3E': 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.
>
> /usr/sbin/named-checkzone -d linuxlighthouse.com

/var/named/linuxlighthouse.com.db
loading "linuxlighthouse.com" from "/var/named/linuxlighthouse.com.db"
class "IN"
zone linuxlighthouse.com/IN: loaded serial 2021042001
OK
 /usr/sbin/named-compilezone -i full -o - linuxlighthouse.com
/var/named/linuxlighthouse.com.db
zone linuxlighthouse.com/IN: loaded serial 2021042001
linuxlighthouse.com.      86400 IN SOA ws.linuxlighthouse.com.
root.linuxlighthouse.com. 2021042001 86400 3600 604800 86400
linuxlighthouse.com.      86400 IN NS ws.linuxlighthouse.com.
linuxlighthouse.com.      86400 IN A 108.220.213.121
linuxlighthouse.com.      86400 IN CAA 0 issue "letsencrypt.org"
mail.linuxlighthouse.com.      86400 IN A 108.220.213.121
ws.linuxlighthouse.com.      86400 IN A 108.220.213.121
ws.linuxlighthouse.com.      86400 IN MX 10 ws.linuxlighthouse.com.
ws2.linuxlighthouse.com.      86400 IN A 108.220.213.122
www.linuxlighthouse.com.      86400 IN A 108.220.213.121
OK
*dig  linuxlighthouse.com http://linuxlighthouse.com a*

; <<>> DiG 9.11.28-RedHat-9.11.28-1.fc32 <<>> linuxlighthouse.com a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43116
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 72bffb4054c2ec9b4b228327608d02f41eb498288e928de9 (good)
;; QUESTION SECTION:
;linuxlighthouse.com. IN A

;; ANSWER SECTION:
linuxlighthouse.com. 86400 IN A 108.220.213.121

;; AUTHORITY SECTION:
linuxlighthouse.com. 86400 IN NS ws.linuxlighthouse.com.

;; ADDITIONAL SECTION:
ws.linuxlighthouse.com. 86400 IN A 108.220.213.121

;; Query time: 1 msec
;; SERVER: 108.220.213.121#53(108.220.213.121)
;; WHEN: Sat May 01 00:27:48 PDT 2021
;; MSG SIZE  rcvd: 125

[jackc@ws etc $ host linuxlighthouse.com
linuxlighthouse.com has address 108.220.213.121

[jackc@ws etc $ *host linuxlighthouse.com http://linuxlighthouse.com*
linuxlighthouse.com has address 108.220.213.121

seems t be working better, how many holes do you see at this point??

thx, ...