Oke first screenshot, very correct. You also will see that the namservers are still ns1.primarydomain.com and ns2.primarydomain.com if not this is correct anyway.
Delete both. In Directadmin you don't set the rDNS/PTR, so you can loose the in-addr.arpa records.And then in Server Manager -> DNS Administration I currently have these 2 records:
I'ts written in my manual to do it in DNS Administration. Not a DNS record, a complete DNS entry as if you would create a new domain. But not under a user account also not as admin in user level.
YES. In DNS Adminstration as admin in admin level. So there you enter server.primarydomain.com as new domain and your server ipv4 and then ns1.primarydomain.com and ns2.primarydomain.com and save.1. I don't need to create a new DNS record on the server for server.primarydomain.com ?
Officially they are reverse dns records. But they won't work if you create them in Directadmin in this case, you need to set the ptr/rdns record at your server provider. So remove all those in-addr.arpa records, you don't need them.2. I assume this [backwards ip address].in-addr.arpa record is my Reverse DNS record.
Correct, that is where the rDNS/PTR is made for both ipv4 and ipv6.c) And then I also need to contact the owner of my IP address and get them to add my rDNS/PTR records.
I don't use Cloudflare, so I don't know how this is working if you are using your own nameservers like ns1.primarydomain.com and ns2.primarydomain.com.And then lastly, there's CloudFlare. This is what I currently have...
server A record there maybe.Maybe @Zhenyapan or @jamgames2 work with cloudflare and can confirm or tell you which records you need additionally in Cloudflare.
I really have to go offline now it's 02.33 already.
برچسب:
نویسنده: ایمان اصلاحی