Just one minor clarification: VeriSign does not control the root servers, only the .com and .net TLDs that the root servers refer to.
Bill ----- Original Message ----- From: John Tolmachoff (Lists) To: [EMAIL PROTECTED] Sent: Monday, September 22, 2003 11:31 AM Subject: RE: [Declude.JunkMail] VeriSteal is stealing traffic from your domain. Problem1. If the AD domain is called 123exampleforme.com, and someone registers that on the internet, you are now according to ICANNA regulations illegally using a registered name. Problem 2. If you do not have forwarders properly configured in the DNS server that is used, you are querring the root servers, which are controlled by Verisign. Therefore, you are subject to that control. This is way it is always recommended that if you are going to use a unregistered domain name in AD, you use a fake TLD, such as .moc or .abc or .mine or such AND have forwarders properly configured. John Tolmachoff MCSE CSSA Engineer/Consultant eServices For You www.eservicesforyou.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Bramble Sent: Monday, September 22, 2003 10:40 AM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] VeriSteal is stealing traffic from your domain. Who says that I have to register the domain that Active Directory is using? My Active Directory name isn't intended to be used on the Internet. In most installations, you look to your own Active Directory server first for the lookups, so if it exists on the Internet it won't interfeer...until now. I think this is one of the issues that ICANN was talking about concerning how the change can have unintended consequences (besides spam blockers). This also looks to be a problem in general with how Microsoft delegates lookups. Their software shouldn't take the root of your Active Directory tree and then append sub-domains to it and turn to the root servers for resolution. That appears to be a security risk if you ask me, and it doesn't make sense to do. Matt John Tolmachoff (Lists) wrote: Ah yes, using an unregistered domain name with a real TLD is a no-no. Whenare people using AD going to get this? AD must be configured correctly or else problems will come up when you leastexpect it. John Tolmachoff MCSE CSSAEngineer/ConsultanteServices For Youwww.eservicesforyou.com -----Original Message-----From: [EMAIL PROTECTED]:[EMAIL PROTECTED] On Behalf Of Matthew BrambleSent: Monday, September 22, 2003 12:52 AMTo: [EMAIL PROTECTED]: Re: [Declude.JunkMail] VeriSteal is stealing traffic from yourdomain. I figured it out. The problem is definitely with Active Directory. Turningoff DNS Client on the local server only created a situation where theirfirst bogus sub-domain would timeout but a retry would still go toSiteFinder. Here's what nslookup returns when directed at the DNS server onthe co-located machine (not running Active Directory): adsfadsfasfdadsf.declude.com Server: ns1.igaia.comAddress: 208.7.179.11 Non-authoritative answer:Name: adsfadsfasfdadsf.declude.com.primary.igaiaoffice.comAddress: 64.94.110.11That's the bogus sub-domain appended to my local Active Directory domain(replaced for security with an equivalent). The issue relates to the factthat my real Active Directory domain name is not registered and lies in the.com namespace, so when the lookup fails on the primary server, it goes backto the local Active Directory server and appends the lookup that produces nomatch to my unregistered Active Directory name, which returns the IP forSiteFinder. If I registered my Active Directory name, I wouldn't bedirected to SiteFinder. Make sense now? Matt
