[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

How to internally reconfigure DNS from a public domain on a windows 2003 server.

Dear Experts,
A client of mine setup their network and used their fully qualified domain name(seatex.com) as their internal domain, instead of using seatex.local or seatex.home. Can you walk me through the steps to help a layman( like myself) to help my client reconfigure his dns. I do not have access to his servers as I work in another state all together!

Ultimatlely, the problem is that he is on a windows 2003 server and all of his employees are networked throught that one server. Thier webmail works but their emails in Outlook are not working because of this internal DNS issue. His email was just converted from an in house Linux server.

Is there is an easy way to resolve this without shutting down their servers for too long?  

Needing help ASAP!

Thank you kindly,

Hollye

0
piratepatrol
Asked:
piratepatrol
4 Solutions
 
The--CaptainCommented:
>A client of mine setup their network and used their fully qualified domain name(seatex.com) as their internal domain, instead
>of using seatex.local or seatex.home

I don't understand why that's a problem - is this a windows-specific issue?  I'm guessing the config is this way because it that's the way it was on the linux box.  I guess what I'm asking is, should I approach this as a DNS problem or a Microsoft issue?

>I do not have access to his servers as I work in another state all together!

www.gotomypc.com

Cheers,
-Jon

0
 
td_milesCommented:
Jon, I'm just guessing, but I think the problem may be that this server is authorative for the domain on the Internet. If they are using private IP address range internally, the DNS is probably responding with internal IP addresses for request like mail.seatex.com, instead of the correct public IP address.

If this is the problem, I don't know if it is easily fixed in Windows (some kind of split DNS arrangement ?). My resolution would be to host the external DNS externally (at ISP), totally seperate from the internal DNS.

If this isn't the problem, then I'm just speculating and should probably shut up right about now :)
0
 
Leon FesterCommented:
Nope none of that is neccessary.. Firstly you need to more accurate identify the problem...What exactly is the problem? What is the name of the server that they are trying to connect to...Are they running an exchange server? How do the access there mail? Is it directly to the ISP, or a local server.

Firstly if they need to access mail.seatex.com then in your DNS zone, create a new MX record and add the FQDN. It could be that they have a server also called mail on their domain so it's possibly looking at that server instead of the correct MX records.

I've worked on many LAN's where the administrators have configured the internal domain with the same name as the FQDN.

Basically you can figure it out yourself if they need to access a mail server, then create a MX record in the DNS zone, with the correct external IP of that server. The reason why their webmail works is because they are accessing the Internet and using the external DNS server to resolve the URL and inversely the IP address that is returned by external DNS is correct. Local doesn't work, 'cos the local DNS server does not have the correct IP address/FQDN in the MX record, or no MX record at all.

FQDN = Fully Qualified Domain Name.
0
 
xrokCommented:
Just create a new Zone to seatex.com on DNS
It should work.

new host www.seatex.com  and put public ip address to that host
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

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