Child Name servers Not updates

domain.tld is my domain and i created two child name servers like ns1.domain.tld and ns2.domain.tld. This domain and its A records added in cloudflare. and my ns1 and ns2 IP is 2.2.2.2.

Now I add these child name servers as name servers for a new domain. but its pointing to another IP like 1.1.1.1 instead of 2.2.2.2

What is the solution for this.

It’s hard to tell since you haven’t used any real names that we can look up. The first thing I would check is that the hostnames you want to use as nameservers are aet to :grey: DNS Only.

its DNS Only. nsw1.mydnsweb.com and nsw2.mydnsweb.com is the child name servers and its real IP configured is 173.249.9.88. But when new domain adds okabcreations.com then with this name servers, its calling the IP 88.198.110.219.

I dont know why its happening.


I am unable to duplicate any query that returns the wrong IP. You might want to try a different tool than intoDNS.

https://toolbox.googleapps.com/apps/dig/

its not working in my side. in google tool its working or showing correctly. in all other tools its showing the wrong IP. theses other tools are correct because, when we try to install SSL on server, then it will shows that the domain is not pointed to the ip

DNSViz is also picking up the bogus IPs on your nameservers.

https://dnsviz.net/d/okabcreations.com/servers/

It looks like there is a glue record in the com. zone. You will need to work with your registrar (for the mydnsweb.com) to purge the invalid glue records for nsw1 and nsw2.

if its corrects then why the following error when we installs SSL

Could not issue an SSL/TLS certificate for okabcreations.com
Details

Could not issue a Let’s Encrypt SSL/TLS certificate for okabcreations.com. Authorization for the domain failed.

Details

Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/353611414832.

Details:

Type: urn:ietf:params:acme:error:dns

Status: 400

Detail: DNS problem: server failure at resolver looking up A for okabcreations.com; DNS problem: server failure at resolver looking up AAAA for okabcreations.com

You will benefit from taking your Let’s Encrypt specific issues to their Community, as it is beyond the scope of the Cloudflare Community. Have you fixed the bad glue records at your registrar yet?

its not lets encrypt issue. its dns error.

The inability to obtain a Let’s Encrypt certificate is absolutely a Let’s Encrypt issue, even if it is being caused by your bad glue records. Have you deleted them from the parent nameservers using your registrar yet? Only your registrar can help you remove the invalid glue records for your nsw1 and nsw2 nameservers. Until you remove those unnecessary and incorrect glue records, you will not make any further progress on this matter.

2 Likes

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.