• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

DNS Subdomain Delegation

B

Blitzrommel

2[H]4U
Joined
Sep 26, 2001
Messages
2,659
So I have a domain, we'll call it example.com. It points to a webhost, and the nameservers are those of the webhost company. I have access to my DNS records, so I can edit my zone. To fully understand terminology, those nameservers are authorative of the domain example.com, correct? So changes I make there, defines my DNS.

I have Active Directory set up here in my home office, with the domain home.example.com. I've set up forward and reverse lookup zones for my network (just a /24 internal network). So, technically my two DNS servers here in my office are authorative for the home.example.com domain, correct? (And yes, I understand the difference between a Windows domain and an internet domain).

I'd like to delegate my subdomain of home.example.com to my servers here in my office. I have a block of public IP addresses (and a business connection, before people start questioning... :)

So basically, example.com's DNS is handled by a webhost nameserver, and I'd like home.example.com's DNS to be handled by my own servers. How do I delegate control of home.example.com to my local nameservers here? (And yes, I understand that it's best practice to have nameservers on different networks!) I'd imagine it just involves adding an NS record to point here, but the NS record can't point to an IP if I recall.

Which brings me to another topic of DNS -- I have the option to have my ISP change my reverse DNS entries for my IP block, or to delegate control of those PTR records directly to me. Which should I choose? I'm setting up exchange server as well, which is why this is important to me.

Hope this is clear enough. :)
 
What I would do, is add a zone in the root DNS that points your IP to that subdomain; you don't have do use a name in that record. I forgot which kind of record it is, but it can be done. Also, even if you get that all pointed correctly, your Windows DNS server will not be authoritative for that subdomain. This is because the Windows DNS server is not truly a DNS server for anyone but your internal /24. It is a DNS "cacher" for everthing else.
 
AMD[H]unter said:
What I would do, is add a zone in the root DNS that points your IP to that subdomain; you don't have do use a name in that record. I forgot which kind of record it is, but it can be done. Also, even if you get that all pointed correctly, your Windows DNS server will not be authoritative for that subdomain. This is because the Windows DNS server is not truly a DNS server for anyone but your internal /24. It is a DNS "cacher" for everthing else.
Click to expand...

I think pointing an IP to a domain is a PTR record, for reverse DNS.
 
I don't have access to my webhost's nameserver's rDNS records... but my ISP allows me to have the rDNS changed on my block of IPs to whatever domain name I want. Or, they can delegate control of my PTR records to me. But as I said, just my ISP can do that.
 
You must log in or register to reply here.
Back
Top