New child domain not resolving publicly

Question

New child domain not resolving publicly

Joe Tynan 0

Created a child domain called 'teamable.humanly.dev' and created a * record to resolve to a specific A record also created in that zone, but nothing is resolving. I also created additional child domains off that, and they are also not resolving. Everything I see in the set up - SOA, NS records, etc. all appear correct.

Joe Tynan 0 Reputation points

2025-04-22T21:41:17.05+00:00

I created the subdomain via the wizard, and I do see a 'teamable' NS record inside the recordset for humanly.dev, as well as a subdomain 'teamable.humanly.dev' in the list of domains in the portal. One thing I did see that seems odd - the NS record for teamable inside the humanly.dev recordset is listing a different set of NS servers than what is displayed with the @ record inside the 'teamable.humanly.dev' recordset. When comparing this to a functional subdomain (staging.humanly.dev, for example,), that 'staging' NS Record inside the humanly.dev recordset and the @ record inside the staging.humanly.dev domain are identical.
Rohith Vinnakota 4,740 Reputation points Microsoft External Staff Moderator

2025-04-22T21:59:35.2933333+00:00

Hi @Joe Tynan

thank you for your reply,

I can see your name servers now.

Kindly let us know if the above helps or you need further assistance on this issue.

Please do consider to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Rohith Vinnakota 4,740 Reputation points Microsoft External Staff Moderator

2025-04-23T17:00:35.5+00:00

Hi @Joe Tynan,

Following up to see if the above suggestion was helpful. And, if you have any further query do let us know.
Rohith Vinnakota 4,740 Reputation points Microsoft External Staff Moderator

2025-04-24T19:21:31.08+00:00

Hi @Joe Tynan,

Following up to see if the above suggestion was helpful. And, if you have any further query do let us know.

1 answer

Your answer

Joe Tynan 0 Reputation points

2025-04-22T21:41:17.05+00:00

I created the subdomain via the wizard, and I do see a 'teamable' NS record inside the recordset for humanly.dev, as well as a subdomain 'teamable.humanly.dev' in the list of domains in the portal. One thing I did see that seems odd - the NS record for teamable inside the humanly.dev recordset is listing a different set of NS servers than what is displayed with the @ record inside the 'teamable.humanly.dev' recordset. When comparing this to a functional subdomain (staging.humanly.dev, for example,), that 'staging' NS Record inside the humanly.dev recordset and the @ record inside the staging.humanly.dev domain are identical.
Rohith Vinnakota 4,740 Reputation points Microsoft External Staff Moderator

2025-04-22T21:59:35.2933333+00:00

Hi @Joe Tynan

thank you for your reply,

I can see your name servers now.

Kindly let us know if the above helps or you need further assistance on this issue.

Please do consider to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Rohith Vinnakota 4,740 Reputation points Microsoft External Staff Moderator

2025-04-23T17:00:35.5+00:00

Hi @Joe Tynan,

Following up to see if the above suggestion was helpful. And, if you have any further query do let us know.
Rohith Vinnakota 4,740 Reputation points Microsoft External Staff Moderator

2025-04-24T19:21:31.08+00:00

Hi @Joe Tynan,

Following up to see if the above suggestion was helpful. And, if you have any further query do let us know.

Answer 1

Hi @Joe Tynan

I understand that you want to create the subdomain.

I can see the parent domain NS records, but I cannot see any NS records for the subdomain.

Ensure that the NS records for teamable.humanly.dev at the parent domain humanly.dev are correctly set up and pointing to the appropriate name servers for the subdomain. Since you mentioned that the NS record for teamable shows a different set of NS servers than expected, that could definitely cause resolution issues.

Subdomain:

User's image

Parent Domain:
User's image

Ensure that the subdomain NS server is correctly added in the parent domain.

Please refer to this document on how to delegate the subdomain:
https://learn.microsoft.com/en-us/azure/dns/delegate-subdomain

Kindly let us know if the above helps or you need further assistance on this issue.

Please do not forget to "Accept the answer” and “Yes” wherever the information provided helps you, this can be beneficial to other community members.

Share via

New child domain not resolving publicly

1 answer

Your answer