I am trying to set up a sub-domain that points to Azure name servers for App Services so we do not have to add records in the main domain.
- Main domain:
example.com> DNS provider's name servers
sub.example.com> Azure name servers.
I tested the theory in two public DNS providers and the process was easy and straight forward. I went to the name server records for the prescribed domain and added:
sub | ns1-02.azure.com sub | ns2-02.azure-dns.net etc...
Therefore, any requests pointing to
*.example.com would be dealt with by the public DNS's name servers and anything pointing to
*.sub.example.com would be dealt with by Azure name servers.
However, we now need to use the customer's actual domain, hosted by Network Solutions and they have a different setup. I can add name servers, however there is no place to add
sub, only the name server's FQDN, therefore it looks like entries here would replace their name server with Azures for everything, which is not what we want to do.
Reading their documentation, on adding a sub-domain, it appears they want me to add what I would refer to as an A-record. http://www.networksolutions.com/support/how-to-create-sub-domains/, however, what would that A record look like.
@ > ns1-02.azure.com I fear that would break things.
How could I achieve this. I am I forgetting something in DNS 101. Is there a work around / trickery anyone can think of that would allow us to achieve the same goal without having to suggest the customer moves away from Network Solutions or buying another domain?