Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 289
  • Last Modified:

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.
0
rajini88
Asked:
rajini88
  • 4
  • 3
3 Solutions
 
Neil RussellTechnical Development LeadCommented:
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
 
Neil RussellTechnical Development LeadCommented:
0
 
rajini88Author Commented:
Hi Neilsr,

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

Cheers,
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
joelgaskellCommented:
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
 
rajini88Author Commented:
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
 
rajini88Author Commented:
Thank you all.
0
 
rajini88Author Commented:
Thank you guys.
0
 
Neil RussellTechnical Development LeadCommented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now