Re: Problem with MX records behind firewall.
On Mon, Jun 02, 2003 at 12:16:30AM +0100, Alan Chandler wrote:
> I am having a problem with Mailman on my internal network with the
> chandlerfamily.org.uk mail addresses. My guess is its doing an MX lookup and
> getting the external address of my netgear box. Unfortunately, the
> port-forwarding does not seem to work when accessing the box from internally.
I have a similar issue with my setup (where the IP address of my server
is a RFC1918 address, and is nat'd through a gateway).
I get around this by ifconfig'ing up the external IP address as an alias
to my network interface.
eg:
eth1 Link encap:Ethernet HWaddr 00:A0:CC:D0:36:21
inet addr:192.168.101.1 Bcast:192.168.101.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6031047 errors:1 dropped:0 overruns:0 frame:0
TX packets:4518341 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3942124702 (3.6 GiB) TX bytes:3202721026 (2.9 GiB)
Interrupt:7 Base address:0xb000
eth1:1 Link encap:Ethernet HWaddr 00:A0:CC:D0:36:21
inet addr:202.181.20.175 Bcast:202.181.20.255 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:7 Base address:0xb000
This means that any hosts on my internal network that try to get to the
'real world' IP address hit the alias, and get passed through without
having to worry about the NAT.
Depending on what your network setup is, this may solve your problem,
and is much easier that dealing with setting up zone files.
--
Andrew Shipton ------------------------------------------------------------
"It is inhumane, in my opinion, to force people who have a genuine medical
need for coffee to wait in line behind people who apparently view it as
some kind of recreational activity." -- Dave Barry
Reply to: