Delegating sub-domain DNS

22 views
Skip to first unread message

Tom Copeland

unread,
Apr 13, 2022, 12:50:50 PM4/13/22
to VegaDNS
I'm trying to delegate DNS for a sub-domain. Here's the scenario:
- Primary domain is capitoltheatre.com and the name servers are ns3.eagle.ca and ns4.eagle.ca
- we have a sub-domain of mail.capitoltheatre.com and want the name servers to be ns0.dns.dotdigital.com (and ns1, ns2)
- I have created a zone file in VegaDNS for mail.capitoltheatre.com and assigned the above name servers as the NS records
- I have also created mail.capitoltheatre.com as a sub-domain within the capitoltheatre.com zone file and created the NS record there too
- doing a host lookup for mail.capitoltheatre.com comes up empty unless I specify the NS to use for the lookup, i.e. host mail.capitoltheatre.com ns0.dns.dotdigital.com

If I use the MXtoolbox tools and do a DNS Check, both the eagle.ca and the dotdigital.com name servers are showing as authoritative but if I'm not mistaken, only dotdigital.com's should be. What am I missing? We are using version 0.9.10 of VegaDNS.

Bill Shupp

unread,
Apr 13, 2022, 2:55:06 PM4/13/22
to veg...@googlegroups.com
Hi Tom,

I don't believe you want the mail.capitoltheatre.com zone defined in two places.  The parent domain, capitoltheatre.com should have NS records to point to the subdomain's name server, i.e.:

etc

(Note that this is not the same things as a zone/domain, as it doesn't have a unique SOA record for mail.capitoltheatre.com)

Then, the DNS server that hosts mail.capitoltheatre.com will have an actual zone/domain of mail.capitoltheatre.com, which will include the SOA record and the same NS records as the delegation above.  That should be all you need.

Hope this helps,

Bill

--
You received this message because you are subscribed to the Google Groups "VegaDNS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vegadns+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vegadns/8468718e-0ab7-49ec-a47f-a9468f1e0eban%40googlegroups.com.

Tom Copeland

unread,
Apr 13, 2022, 3:40:52 PM4/13/22
to VegaDNS
Thanks, Bill. I'll let you know in 3600 seconds ;-)

-tom

Tom Copeland

unread,
Apr 13, 2022, 3:55:15 PM4/13/22
to VegaDNS
Bill:

That worked! Thank you. I could have sworn I tried it that way last week but apparently not.

Cheers,

-tom
Reply all
Reply to author
Forward
0 new messages