rajini88
asked on
Search Mx Records from Different Domain
Hello there,
Assumed I had trusted a new domain in my primary domain and called 'Hello' any mine 'WhoMe'. I have included Domain 'Hello' MX records into my DNS servers which is part of my range of Windows 2003 AD servers. I can see the new trusted domain in my Domain List at the client desktop. I can ping new domain IP addresses. Connection is OK.
But when I tried to ping the Server Name for example (1.1.1.2 =Teddy) it shows request timed out but no issue with ping the server IP. The solution provided by Microsoft is I need to ping the Server Name together with the Domain Name, e.g Teddy.Hello.com
I could see Teddy in my DNS servers but I can't understand why system can't resolve the Server Name from my DNS or even I have included 'Hello' Domain DNS IP in my DNS Servers range. Can't it accept Teddy instead Teddy.Hello.com?
The issue is my SQL script understand the server name as Teddy and not Teddy.Hello.com. So it would be a huge change in the SQL script and more if the system can't resolve the MX records.
Please help and thank you.
Assumed I had trusted a new domain in my primary domain and called 'Hello' any mine 'WhoMe'. I have included Domain 'Hello' MX records into my DNS servers which is part of my range of Windows 2003 AD servers. I can see the new trusted domain in my Domain List at the client desktop. I can ping new domain IP addresses. Connection is OK.
But when I tried to ping the Server Name for example (1.1.1.2 =Teddy) it shows request timed out but no issue with ping the server IP. The solution provided by Microsoft is I need to ping the Server Name together with the Domain Name, e.g Teddy.Hello.com
I could see Teddy in my DNS servers but I can't understand why system can't resolve the Server Name from my DNS or even I have included 'Hello' Domain DNS IP in my DNS Servers range. Can't it accept Teddy instead Teddy.Hello.com?
The issue is my SQL script understand the server name as Teddy and not Teddy.Hello.com. So it would be a huge change in the SQL script and more if the system can't resolve the MX records.
Please help and thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Neilsr,
Thank you for your prompt feedback. Let me configure the Forward DNS and update you status.
Cheers,
Thank you for your prompt feedback. Let me configure the Forward DNS and update you status.
Cheers,
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you all.
ASKER
Thank you guys.
While your solution may work for your exact setup, it is not the "Correct" way to do it. By doing what you are doing you are setting a DNS server in a foriegn domain for the LOCAL PC. This is a no no for Domain computers.
You will now generate DNS lookups over the networks to the wrong servers from every PC.
Had you created a DNS forwarder on your own DC for the the other domain and vice versa, then it would cache that once looked up and your network traffic would be drastically reduced.
Glad its working anyway.
You will now generate DNS lookups over the networks to the wrong servers from every PC.
Had you created a DNS forwarder on your own DC for the the other domain and vice versa, then it would cache that once looked up and your network traffic would be drastically reduced.
Glad its working anyway.
You need to configure a dns forwarder AND configure you SQL server (Host that runs the script) to use additional DNS suffixes, that of Teddy of course.