[zeezam]

Have an external IP address binded to a dns name mail.company.com in our dns entry on a windows 2003 server. The issue that I have is when you try to reach the server internal with that dns name it tries with the external IP address and fail.

On our local network we have not the *.com, only *.local.
Don't know how to solve that issue nice and easy without edit host files on all clients...

 

[zerofire]

If you have set up the gateway and DNS properly to allow traffic out to the net you should not have issues with failing when doing a loop from an external ip address. If you set the ip address as the one that is external and it is a dynamic ip then you are in a jam because it can change. If you have a router or any other network device between your server and the internet then you need to set the appropriate forwarding on specific ports.

 

[zeezam]

If you have set up the gateway and DNS properly to allow traffic out to the net you should not have issues with failing when doing a loop from an external ip address. If you set the ip address as the one that is external and it is a dynamic ip then you are in a jam because it can change. If you have a router or any other network device between your server and the internet then you need to set the appropriate forwarding on specific ports.

It's not dynamic and we have set an internal ip adress on the server ip configuration so we use the ip adress internal or if you use the hostname on the server but with dns it fails.

 

[zerofire]

Can you clarify this a bit because now my head is spinning a bit.
Is this the issue:
On the 2003 servers console you want to use the URL to access the server but it then has a DNS issue.
Or is this the issue:
A pc(not the server) on the intranet is trying to use the URL to access the server but gets a DNS issue.

 

[zeezam]

Can you clarify this a bit because now my head is spinning a bit.
Is this the issue:
On the 2003 servers console you want to use the URL to access the server but it then has a DNS issue.
Or is this the issue:
A pc(not the server) on the intranet is trying to use the URL to access the server but gets a DNS issue.

The problem is from the PC (clients).

When they try to access mail.company.com internal it tries with the external address.

 

[lowkey77]

No, the problem is the firewall/router. If the device detects the IP you are looking for on the "internal" and the request is from the internal as well, the traffic will drop.
try this
http://servername/exchange (might need to be HTTPS:// depending on how you set it up.)

 

[FSGDAG]

If I'm understanding this correctly you have an internal domain with a .local. You also have a mail server but your clients are using the .com domain. When client ( workstation ) computers try to access the .com name, your unable to resolve it.

This is probably due to a loop back where your unable to go out the net only to be sent directly back.

How do you get around this??? In your internal DNS server you have a forward lookup zone of <domain-name>.local. Add an additional forward lookup zone with the domain your trying to access. Next, create an 'A' record in DNS for 'mail' with the internal IP address of the server your trying to reach.

If you have a website or other 'A' records for that domain you'll also need to add them as well

Hopefully I explained this easy enough for you to understand. If you need additional help, please let me know

 

[zeezam]

If I'm understanding this correctly you have an internal domain with a .local. You also have a mail server but your clients are using the .com domain. When client ( workstation ) computers try to access the .com name, your unable to resolve it.

This is probably due to a loop back where your unable to go out the net only to be sent directly back.

How do you get around this??? In your internal DNS server you have a forward lookup zone of <domain-name>.local. Add an additional forward lookup zone with the domain your trying to access. Next, create an 'A' record in DNS for 'mail' with the internal IP address of the server your trying to reach.

If you have a website or other 'A' records for that domain you'll also need to add them as well

Hopefully I explained this easy enough for you to understand. If you need additional help, please let me know

You understand correctly.
I want to access the server with the mail.company.com address on the .local intranet. I can access the server with <hostname>.local but then it's not a universal name, I want to access with the same name as outside.

I'll try to add an forward lookup zone and the A record.

 

[FSGDAG]

You understand correctly.
I want to access the server with the mail.company.com address on the .local intranet. I can access the server with <hostname>.local but then it's not a universal name, I want to access with the same name as outside.

I'll try to add an forward lookup zone and the A record.

Good... Glad I got that correct :grin:

The forward lookup zone and "A" record(s) will work for you then. Make sure to add an "A" record for each service you need to access. Example :

mail, www, ftp, etc.

 

[zeezam]

Good... Glad I got that correct :grin:

The forward lookup zone and "A" record(s) will work for you then. Make sure to add an "A" record for each service you need to access. Example :

mail, www, ftp, etc.

This worked out! Thanks alot.

 

[FSGDAG]

No problem!! Glad I could be of help!