NS records for a subdomain

What is the name of the domain?

acc com

What is the issue you’re encountering

I have created NS records in cloudflare, but they are not propagating

What steps have you taken to resolve the issue?

Since the domain registrar is Network Solutions, I reached out to them to ask. I thought that since the NS records for the domain exist there, then maybe the subdomain records could be added. They stated that I could, but would have to move management of DNS back to them, which I do not want to do. I have created the NS records in cloudflare as instructed my NetSol. I can dig the records if I specify an authoritative an authoritative server, but I do not see the records using any other public DNS server.

What feature, service or problem is this related to?

Nameservers

Original question: i want to create NS records for a subdomain. Network Solutions is the registrar for the domain and the NS records point to cloudflare. I have created NS records in cloudflare, but they do not seem to be propagating. Is there another step I need to take? NetSol states that there can only be root domain NS records on their system

What is the subdomain you are trying to delegate?

mc acc com

Looks all good to me, but you don’t seem to have any DNS records at the target nameservers:

dig +trace +nodnssec mc.acc.com

...

acc.com.                172800  IN      NS      rick.ns.cloudflare.com.
acc.com.                172800  IN      NS      tara.ns.cloudflare.com.
;; Received 355 bytes from 192.35.51.30#53(f.gtld-servers.net) in 10 ms

mc.acc.com.             300     IN      NS      ns1.exacttarget.com.
mc.acc.com.             300     IN      NS      ns2.exacttarget.com.
mc.acc.com.             300     IN      NS      ns3.exacttarget.com.
mc.acc.com.             300     IN      NS      ns4.exacttarget.com.
;; Received 123 bytes from 2606:4700:50::adf5:3ae1#53(tara.ns.cloudflare.com) in 3 ms

;; Received 39 bytes from 104.225.42.129#53(ns3.exacttarget.com) in 30 ms
2 Likes

@Laudian - Thank you for the verification! The vendor is going to set up additional records they need for the “mc” subdomain.

Is there a reason I do not see these when I run a dig command with NS on a public DNS server (like google)? I see the NS servers for the root domain when I do this, but not the subdomain

Yes.

Have a look at this:

What you see in the red rectangle are the authoritative NS records, reported by the authoritative nameservers. These are what is returned by an NS query.

In the step above that, you see exactly the same records, but they are delegation records, not authoritative.

Let’s repeat the same for your domain:


You can see that there are no NS records in the red square. That means there is no authoritative NS data that could be returned in a query.

dig +short laudian.de ns @1.1.1.1
perla.ns.cloudflare.com.
syeef.ns.cloudflare.com.

dig +short mc.acc.com ns @1.1.1.1

2 Likes

@Laudian can you tell my why are there no authoritative records? Should those not be the the cloudflare NS records?

Will this cause an issue or should the vendor be fine to proceed with creating the records they need for the subdomain?

This usually means that you have not added the subdomain to the nameservers you are delegating to yet, so the nameserver can’t respond with NS records.

2 Likes

Understood. Thank you so much for the help!

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