Conditional forwarding for existing zone? Phillip.Strang[ at ]gmail.com 5/9/2007 3:05:57 PM I have a client with a long established internal domain name of "US". The domain name was setup many years ago (prior to the existance of the top level .us domain). Consequently, we have a .us AD integrated zone running on the network. The obvious problem comes when a client needs to perform name resolution for a host on the public TLD, the internal DNS server doesn't find a matching entry (it's the SOA for .us internally). We are trying to avoid going through a complete domain renaming process if we can get around this issue with a DNS fix. What I'd like to do is similiar to a conditional forward (but not quite??) - any .us host names that cannot be resolved internally would be forwarded out to the ISP for an attempted lookup. Any ideas on how to accomplish this without breaking internal AD/DNS would be much appreciated.

Re: Conditional forwarding for existing zone? "Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 5/9/2007 5:46:11 PM Read inline please. In news:1178723157.650906.8730[ at ]e51g2000hsg.googlegroups.com, Phillip.Strang[ at ]gmail.com <Phillip.Strang[ at ]gmail.com> typed: [Quoted Text] > I have a client with a long established internal domain name of "US". > > The domain name was setup many years ago (prior to the existance of > the top level .us domain). Consequently, we have a .us AD integrated > zone running on the network. > > The obvious problem comes when a client needs to perform name > resolution for a host on the public TLD, the internal DNS server > doesn't find a matching entry (it's the SOA for .us internally). We > are trying to avoid going through a complete domain renaming process > if we can get around this issue with a DNS fix. > > What I'd like to do is similiar to a conditional forward (but not > quite??) - any .us host names that cannot be resolved internally would > be forwarded out to the ISP for an attempted lookup. > > Any ideas on how to accomplish this without breaking internal AD/DNS > would be much appreciated. If the AD DNS name is us, you're stuck, unless you rename the domain. You should probably do a rename or migration because of the other issues caused by a single-label DNS name, but that's your decision to make. DNS will not forward any name for which it should be authoritative for, meaning it will not forward any name in the .us TLD tree that is not specifically delegated. -- Best regards, Kevin D. Goodknecht Sr. [MVP] Hope This Helps Send IM: http://www.icq.com/people/webmsg.php?to=296095728 =================================== 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 ===================================

Re: Conditional forwarding for existing zone? "Herb Martin" <news[ at ]learnquick.com> 5/9/2007 8:11:28 PM <Phillip.Strang[ at ]gmail.com> wrote in message news:1178723157.650906.8730[ at ]e51g2000hsg.googlegroups.com... [Quoted Text] >I have a client with a long established internal domain name of "US". Single label domain names are a serious problem issue in AD/DNS for Microsoft. > The domain name was setup many years ago (prior to the existance of > the top level .us domain). Consequently, we have a .us AD integrated > zone running on the network. Ugh. He can now resolve NOTHING in the US domain and there is no good solution. > The obvious problem comes when a client needs to perform name > resolution for a host on the public TLD, the internal DNS server > doesn't find a matching entry (it's the SOA for .us internally). We > are trying to avoid going through a complete domain renaming process > if we can get around this issue with a DNS fix. > > What I'd like to do is similiar to a conditional forward (but not > quite??) - any .us host names that cannot be resolved internally would > be forwarded out to the ISP for an attempted lookup. Won't work that way, once you conditionally forward or otherwise resolve US, you are done for it and ALL of its children. YOu would need a list of EVERY child domain in US, and it would have to be kept current (nearly impossible) to define every child as either delegated (as the real .US does) or conditonally forwarded. > Any ideas on how to accomplish this without breaking internal AD/DNS > would be much appreciated. Rename the domain. It's a problem anyway as a single label domain name. You will first need to reach Win2003 Forest Functional Level. (All DCs running 2003 in every domain of the forest.) -- Herb Martin, MCSE, MVP http://www.LearnQuick.Com (phone on web site)