Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / DNS / October 2003

Tip: Looking for answers? Try searching our database.

NT 4.0 DNS

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Chris - 15 Oct 2003 17:26 GMT
I am having a problem with my DNS I believe.

When sending email to company.com it comes back as "no
route found to company.com." I have added the appropriate
entries to the NT 4.0 DNS server and still...no dice.

Here's the kicker.  I have a development network with W2K
DNS.  When I point the email server to use that
DNS...bingo! It works.  Since it's development, I can't
use that DNS server for prod.

I have a feeling that the records returned for MX records
for company.com are 'aliases' that my NT 4.0 DNS doesn't
know how to handle these.

Anyone...please help!
Jeff Cochran - 16 Oct 2003 14:06 GMT
>I am having a problem with my DNS I believe.
>
>When sending email to company.com it comes back as "no
>route found to company.com." I have added the appropriate
>entries to the NT 4.0 DNS server and still...no dice.

No route means it can't get there from here, not that it doesn't know
where there is.  Normally, you wouldn't have DNS entries for a
destination outside your domain in your DNS.

>Here's the kicker.  I have a development network with W2K
>DNS.  When I point the email server to use that
>DNS...bingo! It works.  Since it's development, I can't
>use that DNS server for prod.

You can use *any* accessible DNS server out there, have you tried
pointing to your ISP's?

>I have a feeling that the records returned for MX records
>for company.com are 'aliases' that my NT 4.0 DNS doesn't
>know how to handle these.

Your DNS doesn't need to know.  Assuming you're not within the same
domain, and you have correctly configured your DNS to forward to an
external DNS, your DNS hands the request off to the outside DNS and
the autoritative DNS for the destination provides the information.

Plus, NT4 handles aliases just fine.

I suspect either your NT4 DNS is misconfigured on forwarding or you
have erroneously entered records for domains outside your authority.
Or you misconfigured the W2K DNS and got lucky...

Jeff
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.