Solved

Search Mx Records from Different Domain

Posted on 2011-09-17
8
252 Views
Last Modified: 2012-05-12
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.
0
Comment
Question by:rajini88
  • 4
  • 3
8 Comments
 
LVL 37

Expert Comment

by:Neil Russell
Comment Utility
Have you created a dns forwarder for the DNS Domain of teddy? I dont know why you talk of MX records, nothing to do with this at all.

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.
0
 
LVL 37

Accepted Solution

by:
Neil Russell earned 250 total points
Comment Utility
0
 

Author Comment

by:rajini88
Comment Utility
Hi Neilsr,

Thank you for your prompt feedback.  Let me configure the Forward DNS and update you status.

Cheers,
0
 
LVL 2

Assisted Solution

by:joelgaskell
joelgaskell earned 250 total points
Comment Utility
You need an A record, not an MX record.  A records translate hostnames to IP addresses.  MX records locate a mail server for a domain.

If you add an A record on your WhoMe domain for teddy, then you should be able to resolve it locally by just using the hostname, but the DNS server will assume you are looking for teddy.whome.com, instead of teddy.hello.com.  It will still return whatever IP address you assigned in your A record, so whether or not that is a problem depends on the content of your SQL script.
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 

Assisted Solution

by:rajini88
rajini88 earned 0 total points
Comment Utility
Hi Guys,

I have found an alternate solution which resolved the problem without handling the DNS server or the hostname file.

You need to added the respecitve Domain DNS server in the Network TCP Properties - DNS tab.  In this case, I had added the Hello & WhoMe.  And at the same DNS tab, select the option 'Append these DNS suffixes (in order)'  So again I added the Domain DNS suffixes for Hello and WhoMe.  You may refer to the attachment for the screen snapshot.

Finally, when system can resolve the Teddy from Domain Hello, it find the next suffixes of a Domain and that would be WhoMe.  You also may find that when you ping the server name, system added the Domain suffixes automatically and this help the search.  Great.

Now, I need to communicate with my Domain Controller team and request them to add this in the DHCP servers for both Domains to resolve the above issue.  

Thank you Guys.

 
DNS-Different-Domain.jpg
0
 

Author Closing Comment

by:rajini88
Comment Utility
Thank you all.
0
 

Author Comment

by:rajini88
Comment Utility
Thank you guys.
0
 
LVL 37

Expert Comment

by:Neil Russell
Comment Utility
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.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Microsoft has released remote PowerShell capabilities to all commercial Office 365 customers. So you can be controlled via PowerShell and not from the Office 365 admin center Download Windows PowerShell Module for Lync Online http://www.micros…
The System Center Operations Manager 2012, known as SCOM, is a part of the Microsoft system center product that provides the user with infrastructure monitoring and application performance monitoring. SCOM monitors:   Windows or UNIX/LinuxNetwo…
This tutorial demonstrates a quick way of adding group price to multiple Magento products.
You have products, that come in variants and want to set different prices for them? Watch this micro tutorial that describes how to configure prices for Magento super attributes. Assigning simple products to configurable: We assigned simple products…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now