No www.google.com<http://www.google.com> in my record, that is the zone name. Where you have your example record below change the left column to read 'same as parent folder' all the way down including the DNAME. In addition to what you show I also have all my name servers in that record of course.
Actually, if you want to ask a question the one that is on my mind is why wouldn't it take the CNAME record when I wanted to add it. It seems to me it should have and that was the suggested solution. Over on another list some of the people are still scratching their head as to why it errored on me when I tried to add the CNAME...leaving the alias blank (same as parent folder) and adding nosslsearch.google.com for the target FQDN. Error was: "A new record cannot be created. An alias (CNAME) record cannot be added to this DNS name. The DNS name contains records that are incompatible with the CNAME record." 2008 R2 integrated DNS. I found references to this error on google with other people trying to do basically the same thing I was trying to do. The fix was to remove all the other records in that zone. My problem was that other than the SOA and NS records I had no other records to remove. The behavior on this seemed to have changed starting with 2003 and up. From: Ben Scott [mailto:[email protected]] Sent: Monday, February 13, 2012 11:50 AM To: NT System Admin Issues Subject: Re: DNS Partial zone CNAMEs? On Mon, Feb 13, 2012 at 9:19 AM, Kennedy, Jim <[email protected]<mailto:[email protected]>> wrote: > I put up a primary zone www.google.com<http://www.google.com> Then I put > up a DNAME leaving the > first line blank )alias name) so that it would use the parent domain. And the > FQDN for the target host as > nosslsearch.google.com<http://nosslsearch.google.com>. I presume you mean something like this? www.google.com<http://www.google.com>. SOA blah blah blah DNAME nosslsearch.google.com<http://nosslsearch.google.com>. I'm not sure that use case -- a DNAME for the current label -- is expected. It seems to be something of a misapplication. DNAME was, as far as I know, intended to map child domains to a new target, not the zone apex. Your use case isn't mentioned explicitly in RFC-2672<http://tools.ietf.org/html/rfc2672>, as far as I can tell. It would appear to run contrary to Section 4.1 Step 3.c (page 4), which states in part: "If at some label, a match is impossible (i.e., the corresponding label does not exist), look to see whether the last label matched has a DNAME record". Since you have to have other records (like SOA) defined for the zone apex, the label exists and should be matched as such. Now, obviously, it works anyway, but one should be wary of depending on undefined behavior. A later change may "fix" it to stop working, or some other software may choke. I'm not saying don't do it. (I'm also not saying do do it.) I just want to point it out. And my reading of RFC-2672 may be wrong. DNAME isn't something I've played with myself. If you want, I can ask over on the DNS ops list. Most of the heavy-hitters in DNS land are subscribed (including the principle authors of the specs, the reference implementation, and several other major implementations), so that's as close to authorative it can get without it being formally specified. OTOH, if you're going to do it anyway, it's academic. :) If you do want me to ask, please let me know what version and service pack of Windows you're running on your servers, and your typical client population. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
