problems receiving e-mail to my server redux

[Ed McCorduck]

> -----Original Message-----
> From: redhat-list-bounces at redhat.com 
> [mailto:redhat-list-bounces at redhat.com] On Behalf Of Ed Greshko
> Sent: Sunday, July 11, 2004 6:00 PM
> To: General Red Hat Linux discussion list
> Subject: RE: problems receiving e-mail to my server redux
> 
> 
> On Sun, 2004-07-11 at 18:20, Ed McCorduck wrote:
> 
> > O.K., I hadn't set port 53 to be forwarded to 192.168.1.101, but I 
> > changed that but still any e-mail sent to me is bouncing. BTW, by 
> > saying "these ports" in your question above, did you mean 
> that there's 
> > a separate port number for udp? All I saw on my router's 
> configuration 
> > screen was that port 53 was for "DNS."
> 
> It would appear that your firewall setting are still not correct.
> 
> When I try to query your DNS server directly I get...
> 
> [root at misty egreshko]# host 24.24.15.155 24.24.15.155
> ;; connection timed out; no servers could be reached
> 
> And a capture on the network shows 24.24.15.155 is still 
> returning an ICMP message of "Destination unreachable" as 
> previously noted.
> 
> I'm not familiar with the configuration of a Linksys 
> router/firewall, but generally speaking it should have a way 
> to indicate that incoming connections using TCP, UDP, or both 
> should be redirected.  But, I guess that isn't needed with 
> Linksys since a quick check on their website indicates....
> 
> "Under the "Forwarding" tab, enter the port(s) that your 
> application uses under the "Service Port" field(s) - type in 
> a number for each of the ports. Both the TCP and UDP ports 
> are activated once you enter a port number in the field."
> 
> Are you certain your nameserver is running?  
> 
> If I do a:
> 
> host 172.16.155.44 172.16.155.44
> 
> where 172.16.155.44 is a server on my network *not* running a 
> nameserver I get a "Destination Unreachable" indication.


[WARNING: The next lines you read emanate from profound Linux/networking
ignorance:]

Hi Ed,

Yes, I installed BIND on my Linux box and set it up to start at every
boot-up, so I assumed this would take care of my DNS/nameserver setup.
One of the bases for that belief is this passage from Peter Harrison's
book _Linux Home Networking II_: "BIND is an acronym for the 'Berkeley
Internet Name Domain' project which MAINTAINS THE DNS RELATED SOFTWARE
SUITE THAT RUNS UNDER LINUX [emphasis mine]. The most well known program
in BIND is 'named', the daemon THAT RESPONDS TO DNS QUERIES FROM REMOTE
MACHINES [emphasis mine again]" (p. 59). Granted, Harrison's book is
full of other details and configurations I must still perform regarding
the files that named uses, but this snippet certainly makes it all sound
simple enough for a fool like me to think I could do it all on my own. 

I'd appreciate your further thoughts on this, and thanks for your reply.



Ed McCorduck
Department of English
State University of New York College at Cortland 
http://mccorduck.cortland.edu 
ICQ: http://mccorduck.cortland.edu/pager 
AIM: EdMcCorduck