On Mon, May 3, 2021 at 6:32 PM Tim via users <users@lists.fedoraproject.org> wrote:
> On Mon, 2021-05-03 at 11:56 -0700, Jack Craig wrote: > > i think you are right, i've been wondering about the ns3's behaviour > > as the dnscheck page keeps telling me i have only one responding dns. > > as it is part of the at&t dns, i have been ignoring this; now is the > > time to deal with it.... > > > > i am sporting mike's recent config file cuz its So much prettier than > > my hack. i hacked in a CAAA record & updated teh serial number giving > > me, ... > > > > $TTL 3D ; default ttl for records without a specified lifetime > > $ORIGIN linuxlighthouse.com. > > linuxlighthouse.com. CAA 0 issue "letsencrypt.org" > > @ IN SOA ws.linuxlighthouse.com. root.linuxlighthouse.com. ( > > 2021050301 ; serial number > > 16384 ; ns refresh > > 2048 ; ns retry > > 1048576 ; authority expiry > > 2560 ); min (RFC2308 ยง4) > > IN NS ws.linuxlighthouse.com. > > IN NS ns3.attdns.com. > > ; IN MX linuxlighthouse.com. > > ws IN A 108.220.213.121 > > IN A 108.220.213.121 > > Are you sure that's constructed properly? There's usually a precise > structure for zone files. All examples I've seen have things in this > these links seem to verify the CAA's record format/content > > https://www.entrust.com/knowledgebase/ssl/how-to-add-caa-record-into-a-dns-zone-file-using-bind-dns > https://www.entrust.com/resources/certificate-solutions/tools/caa-lookup > <https://www.entrust.com/resources/certificate-solutions/tools/caa-lookup> > > $origin . > $TTL > SOA ( > serial > refresh time > retry time > expiry time > minimum time > ) > NS > A > MX > followed by the rest of your records > > I'm not sure about where you might add a new thing, like CAA, but I > wouldn't rearrange the order of that other things without being sure > about it. > > > as an aside, if i add 'www in a 108.220.213.121' > > > > would properly define 'www.linuxlighthouse.com' ??? > > Yes, anything you put left of IN A, that doesn't end in a dot, is a > sub-domain (the server appends your domain name to it). > i've been challenged finding these rules... Thx! is this record format spelled out somewhere, RFC??? perhaps?? > > -- > > uname -rsvp > Linux 3.10.0-1160.25.1.el7.x86_64 #1 SMP Wed Apr 28 21:49:45 UTC 2021 > x86_64 > > Boilerplate: All unexpected mail to my mailbox is automatically deleted. > I will only get to see the messages that are posted to the mailing list. > > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure >
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
