We detected multiple Cloudflare nameserver pairs for eany.org. If you are making DNS changes with no effect, you may be in the wrong account for this domain. The domain could also have been currently or recently added to another Cloudflare account, or deleted and added back to an account. Only the account using the Cloudflare nameservers currently set at the registrar can control this domain.
thank you for your insight and the info from this tool. I am not the owner of the DNS solution, just a user that was given the access I have. Your feedback has been invaluable. I have reached out to the person with higher authority and access and informed them of what you report. Makes sense in that I am working in a zone file that is not connected to the name servers authoritative for this domain.
Here is something I still dont understand. When I do an nslookup and set server to the NS in the zone file I have access to an I query that server for records I placed in that zone file. The M X does not resolve. One would think when I query the actual server I am creating DNS records in, it should resolve
example
NS is jamie.ns.cloudflare.com (as indicated at the bottom of the zone file page in the eany.org account I have access to
I have multiple mail exchanger records configured in the eany zone file on the jamie.ns server
I set my nslookup tool to the jamie server and set type=m x then query that server for ‘mailbag.eany.org’ it comes back a none found
You’re not in the correct Cloudflare account to manage records for this zone. This zone is managed by the following nameservers according to whois. You should route this request to the administrator(s) with permission to maange public DNS for this zone.
Name Server: jen.ns.cloudflare.com
Name Server: ruben.ns.cloudflare.com