I have a subdomain abc.domain.com, which is delegated (it is run by someone
else)
Can I create an A record for host.abc.domain.com on MY server?
Thanks
Blake
In news:eSp0Q0d4...@TK2MSFTNGP03.phx.gbl,
If all you need is one name host.abc.domain.com, you can create a forward
lookup zone named "host.abc.domain.com" (without the quotes), then create
one new host record in the zone, leave the name field blank and give it the
name you need host.abc.domain.com to resolve to. If there are other names
under abc.domain.com, you need resolved differently than they are already
resolved, create the zone named "abc.domain.com", in the zone create the
record named host and/or any other name you need to resolve.
--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
I was thinking, wouldn't the "abc" subdomain's DC/DNS already have the Zone
for "abc"? Wouldn't it be better for the admin of the "abc" Child domain to
just create the Host Record (if it isn't already done Dynamically) and the
whole Forest would already know about it via the normal replication? I used
to be in a Child Domain before we got sold to another company and that is
how it worked for us. No one ever created zones/records for my hosts higher
up in the Forest.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Kevin D. Goodknecht Sr. [MVP]" <ad...@nospam.WFTX.US> wrote in message
news:OCXj1Zf4...@TK2MSFTNGP03.phx.gbl...
In news:eY2Yhgg4...@TK2MSFTNGP02.phx.gbl,
Phillip Windell <philw...@hotmail.com> wrote:
> Hi Kevin,
>
> I was thinking, wouldn't the "abc" subdomain's DC/DNS already have
> the Zone for "abc"? Wouldn't it be better for the admin of the "abc"
> Child domain to just create the Host Record (if it isn't already done
> Dynamically) and the whole Forest would already know about it via the
> normal replication? I used to be in a Child Domain before we got
> sold to another company and that is how it worked for us. No one
> ever created zones/records for my hosts higher up in the Forest.
If I read Blake's original post correctly, he said someone else delegated
abc.domain.com to his DNS and didn't say anything about already having a
zone in that domain tree on his DNS. That being the case, a zone named
abc.domain.com needs to be created. Thinking of it, even if a domain.com
zone already existed, it should still be a separate zone, containing the NS
record with the same name the delegating DNS server uses.
I run domain.com.
Somebody else runs abc.domain.com - so my users can resolve it, it is
delegated in my AD DNS to somebody else (running BIND, not that that matters
here).
The owner of abc.domain.com wants to advertise ns.abc.domain.com as the
nameserver for abc.domain.com.
Right now I have a simple delegation for abc.domain.com pointing to
ns.abc.domain.com. Problem: my users can't resolve ns.abc.domain.com, so
the delegated zone isn't doing me any good. And I can't create an A record
for something that 'belongs' in that delegated zone.
I think a stub zone is the answer. I would create a stub for
abc.domain.com, pointing to the NS boxes for that domain - and it should
behave similiar to the delegation, but I'll have an A record available (in
the stub zone).
Thoughts?
Blake
"Kevin D. Goodknecht Sr. [MVP]" <ad...@nospam.WFTX.US> wrote in message
news:%232eWcyo...@TK2MSFTNGP05.phx.gbl...
Blake
"Kevin D. Goodknecht Sr. [MVP]" <ad...@nospam.WFTX.US> wrote in message
news:OCXj1Zf4...@TK2MSFTNGP03.phx.gbl...
Blake
"Phillip Windell" <philw...@hotmail.com> wrote in message
news:eY2Yhgg4...@TK2MSFTNGP02.phx.gbl...
In news:uwKJVrq4...@TK2MSFTNGP02.phx.gbl,
Blake <blake....@gmail.com> wrote:
> Thanks, guys for your input to date.
>
> I run domain.com.
>
> Somebody else runs abc.domain.com - so my users can resolve it, it is
> delegated in my AD DNS to somebody else (running BIND, not that that
> matters here).
>
> The owner of abc.domain.com wants to advertise ns.abc.domain.com as
> the nameserver for abc.domain.com.
>
> Right now I have a simple delegation for abc.domain.com pointing to
> ns.abc.domain.com. Problem: my users can't resolve
> ns.abc.domain.com, so the delegated zone isn't doing me any good. And I
> can't create an A record for something that 'belongs' in that
> delegated zone.
> I think a stub zone is the answer. I would create a stub for
> abc.domain.com, pointing to the NS boxes for that domain - and it
> should behave similiar to the delegation, but I'll have an A record
> available (in the stub zone).
Follow my original example by creating a forward lookup zone named
"ns.abc.domain.com" with the single @ host record with the IP of the server.
This will act as your Glue and will only resolve that name, All other names
in abc.domain.com will follow the delegation.