On 22/04/2021 04:47, Jack Craig wrote:
i have zone files for llh & reverse zone
Oh, BTW, there is very little point in defining zone "213.220.108.in-addr.arpa" { type master; You only have been assigned 8 IP addresses (6 usable + network + broadcast) within the zone out of 255. I've not heard of any ISP delegating a portion of an in-addr.arpa zone to clients when they are that small. Especially a Master, for that is certainly wrong. It seems you've already told AT&T about 108.220.213.121 and they have entered that into their zone maps. [root@meimei ~]# host 108.220.213.121 121.213.220.108.in-addr.arpa domain name pointer ws.linuxlighthouse.com. Also, in the event I wasn't clear, the sample named.conf was to just run a caching name server to verify that binding will happen to all available interfaces as it should. Once that is accomplished you can go about making changes to that file to service your zones. I would do that step by step and not make wholesale changes. FWIW, I agree with others (and that is what I do) in the the best thing to do is have Network Solutions handle your public DNS and just have a DNS setup for internal use. I go even a step further at home since my home isn't "complex". My NAS has a built-in DNS server with a web interface making it a snap to administer. Why spend time on something you're probably not going to touch? And why expose services to the world that are open to attack if you can have them hosted elsewhere? -- Remind me to ignore comments which aren't germane to the thread. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure