THe title explains it all.

I need to join a MAC to our Windows domain. I have no idea how!

Google is your friend: joining a mac to a windows domain - Google Search (http://www.google.com/search?source=ig&hl=en&rlz=&=&q=joining+a+mac+to+a+windows+domain&btnG=Google+Search)

I can Google all day but I found multiple answers and multiple ways of doing ti=his. None are broken down as simple as I need them (hey I'm a windows guy :D)

more research is in order!

(just because my avatar is an apple doesn't mean I like them) ;)

Sorry about that. I haven't personally had the pleasure of adding a Mac to a Windows domain. There are very few Apple specialists on this site though, you may be better off finding a friendly mac forum.

I figured as much and I have but I always give AMHD the first crack at it.

NK- know anything about Cache poisoning? I started a new thread!

As a hacker method? I've heard of it and of some recent events surrounding the exploit but I'm in no way knowledgeable about DNS servers that way.

Not as in I want to poison cache but it has happened to us a work I believe and I'm trying to find a way to fix it, it can be anywhere from either of our servers are infected, just our clients (virus going around office) and even our forwarding DNS servers.

Wondering how to pinpoint where the misdirected DNS queries are coming from. Servers, Client's local cache or both?

Flush and see if it re-occurs?

Edit to add: unless flushing means you have to rebuild tables/files

We have flushed the local and cleared the cache on all servers.

However you got me thinking. I can pinpoint it by doing one at a time instead of just both.

For example.

A local PC is trying to go to unum.com
They are DNS query is resolved with a rogue IP.
Usually I flush their DNS and the servers and it works, but if I do it seperatly I can narrow down the issue. Hmmm am I correct?

By flushing DNS on the local machine it is then forced to pull from the DNS Servers for first time resolution and then it stores that resolved IP in its cache. If I do this and the DNS returns the same rogue IP I have narrowed it down to the DNS Server it pulled the IP from. If the DNS Server returns the correct IP (and I didn't clear the server cache) I narrowed it down to a client issue.

Does this sound right? I am thinking myself into circles :(

We can close this thread and I will post on the new thread I opened. I have updated some stuff on there!

Thanks NK for offering advise, it helps!