Actually when I was creating the 'a' record in the zone board.imcu.com I
left the name blank (It said it would use the parent name if left blank.).
I did this because I have other imcu.com records that I do not maintain. My
web site provider hosts those records for www.imcu.com.
When I made the 1st attempt I only had a imcu.com zone and the www.imcu.com
began failing all over my internal network.
pop.imcu.com and smtp.imcu.com began failing as well. So I thought I would
narrow the scope of my zone by going with board.imcu.com.
It seems to make sense to me and it is working in this environment.
Thanks for the review though.
--------------------------------------------------
From: "Richard Stovall" <[email protected]>
Sent: Monday, November 16, 2009 9:20 PM
To: "NT System Admin Issues" <[email protected]>
Subject: Re: https and certs issues
OK. But I don't understand how creating nothing but a zone named
board.imcu.com would successfully resolve back to an ip address the
browser could use. I realize that he can have an A record for 'board'
in the imcu.com zone and also have a board.imcu.com zone without any
violation, but how does it resolve for the client if the former isn't
present. An A record for 'board' in the latter would resolve to
board.board.imcu.com. And now I'm 2Xbored and am calling it a night.
Cheers,
Richard
On Mon, Nov 16, 2009 at 5:44 PM, Ben Scott <[email protected]> wrote:
On Mon, Nov 16, 2009 at 4:08 PM, Richard Stovall
<[email protected]> wrote:
The zone should be 'imcu.com' with an A record for 'board' pointing to
the internal ip.
There is nothing wrong with <board.imcu.com> having both an SOA
record and an A record.
Indeed, most second-level domains are configured this way.
<microsoft.com.> has an SOA record and an A record, for example.
It's a popular misconception that <example.com.> is a "domain name"
and <www.example.com.> is something-else-but-not-a-domain-name.
They're all domain names. <com.> is a domain name.
<www.microsoft.com.> is a domain name.
<very.long.domain.name.example.com.> is a domain name. They're all
domain names.
Any domain name can have one or more resource records.
There's nothing special about domain names that identify zones,
other than the SOA record.
If <www.microsoft.com.> has an SOA record, and <microsoft.com.> also
has NS records delegating <www.microsoft.com.> to other nameservers,
than <www.microsoft.com.> becomes a zone of authority.
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
