BlueChimera

Okay guys. I have a AD/DC DNS that should not have gotten advertised externally but was anyway.

Now I am getting DOS attacks for ns1.domain.xxx and ns2.domain.xxx.

Yes these ARE the 2 DNS servers but they are also have aliases of server1.xxxx.xxx which is what we use internally to communicate over AD.

Here is my question.....If I were to set up false A records and direct ns1(2).domain.xxx to say a bogus IP addy...maybe something 10(dot)... Would this help with the DOS attacks aimed towards NS1 and NS2?

I am assuming thse are DNS attacks form malware using ns1.domain.xxx as DEFAULT means of attack. As these same servers are NOT being queried via 53 usinag their alternate names. There is an AUTHORATATIVE resonse via nslookup and a record showing our OTHER DNS servers attached to the domain, and yet these are not getting attacked....hence my theory of automated attack based on defaults for ns1.domain.xxx.

PS This nighmare was all inherited with NO documentation.

How does being 'second named insured' differ from being listed as a 'driver' under someones auto insurance policy? For example say my boyfriend is listed as a 'driver' in my policy but his SNI status is 'no' does it mean he is covered? And if he is covered how would being an SNI differ?

I read on the SoapCentral http://www.soapcentral.com/atwt/news/2006/0703-hen... site that it was a suicide. But then I read nothing was confirmed. And because of the sensitivity of the subject to his family all rumours/speculations are prohibited in the forums. Understandably so, just in case any family members decide to seek support through reading fans condolences.