Ok I guess if I explain the topology of the network and then background of my situation first this posting will be more comprehensive.
We are a small company setting up a brand new network using a registered mydomain.com. This network consists of two windows 2000 servers and some clients. One server box which we will call box01 is the ADC, while the second, box02 is running exchange 2000.
box01.mydomain.com = dns and web server
box02.mydomain.com = mail server
Here is where it gets muddy. This network is behind a cable connection ISP which:
a) only assigns dynamic IP's
b) filters port 80.
To get around this we are running a dynamic name server service which reads our dynamically assigned WAN IP every ten minutes and accepts all external traffic directed to mydomain.com relays it to a differnt port then passes it along to the our networks router using which ever dynamically assigned IP is in existence at that moment. The router in turn forwards web content to box01.mydomain.com and mail content to box02.mydomain.com through appropriate ports. Because this service records the dynamic changes in our WAN IP and forwards the request along, the domain in essence has a static IP.
Behind the router I have hard coded static IP's for both servers and have entered in the appropriate A records for both on the DNS server residing on box01.mydomain.com.
When I do an nslookup outside the lan all addresses, name servers and mx are correct. Mail can be sent with the mail exchanger mail.mydomain.com. This leads me to believe the dynamic name server service is cofigured correctly and resolves the mail exchanger correctly as well.
On the inside an nslookup results in loopback addresses and an mx of box2.mydomain.com and mail can not be sent using mail.mydomain.com This leads me to believe that the mail exchanger is not being resolved correctly or atleast the way I would like for it to and that the problem is in the DNS server internally.
I created an mx record in the dns pointing to box02.mydomain.com but I feel I am still doing something wrong.
I would like to use mail.mydomain.com as an incoming mail server on both inside and outside the lan. Am I crazy for this?
What should my MX record look like in my internal DNS?
Is it normal for the difference between internal and external?
Can anyone suggest a solution?
Does anyone have any comments?
Thank you
-j
We are a small company setting up a brand new network using a registered mydomain.com. This network consists of two windows 2000 servers and some clients. One server box which we will call box01 is the ADC, while the second, box02 is running exchange 2000.
box01.mydomain.com = dns and web server
box02.mydomain.com = mail server
Here is where it gets muddy. This network is behind a cable connection ISP which:
a) only assigns dynamic IP's
b) filters port 80.
To get around this we are running a dynamic name server service which reads our dynamically assigned WAN IP every ten minutes and accepts all external traffic directed to mydomain.com relays it to a differnt port then passes it along to the our networks router using which ever dynamically assigned IP is in existence at that moment. The router in turn forwards web content to box01.mydomain.com and mail content to box02.mydomain.com through appropriate ports. Because this service records the dynamic changes in our WAN IP and forwards the request along, the domain in essence has a static IP.
Behind the router I have hard coded static IP's for both servers and have entered in the appropriate A records for both on the DNS server residing on box01.mydomain.com.
When I do an nslookup outside the lan all addresses, name servers and mx are correct. Mail can be sent with the mail exchanger mail.mydomain.com. This leads me to believe the dynamic name server service is cofigured correctly and resolves the mail exchanger correctly as well.
On the inside an nslookup results in loopback addresses and an mx of box2.mydomain.com and mail can not be sent using mail.mydomain.com This leads me to believe that the mail exchanger is not being resolved correctly or atleast the way I would like for it to and that the problem is in the DNS server internally.
I created an mx record in the dns pointing to box02.mydomain.com but I feel I am still doing something wrong.
I would like to use mail.mydomain.com as an incoming mail server on both inside and outside the lan. Am I crazy for this?
What should my MX record look like in my internal DNS?
Is it normal for the difference between internal and external?
Can anyone suggest a solution?
Does anyone have any comments?
Thank you
-j