Re: a problem reaching pilotalk.com from the outside of my lan

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2007-07-22 at 19:52 -0500, Scott Berry wrote:
> I have a mysterious problem here.  I tried to validate WWW.pilotalk.com with 
> the w3c validator to see if things were working right beyond my LAN and 
> apparently they are not.  I got the following error:
> Sorry! This document can not be checked.
> 
> I got the following unexpected response when trying to retrieve <
> http://www.pilotalk.com/>:
> 
> 500 Server closed connection without sending any data back

I'm not getting anything from trying to browse to the website
<http://www.pilotalk.com/> at the moment.  There's no response.  Is the
server running?

> I have an A record pointing at WWW.pilotalk.com.  I am assuming this is 
> correct right.  

Is your IP address for your domain name up to date?  It resolved to
67.54.156.70, but now I'm not getting any resolution.  I must have seen
a cached result, which has expired in the middle of my testing it.

> Also I believe it was Tim that mentioned about changing my 
> hosts so it would look like mail.pilotalk.com.  Now will this foul up my 
> pilotalk.com host?  Cause I am running mailman and the web server and will 
> be running bugzilla and svn all on the same server.  So how should I set up 
> my /etc/hosts for this one?

That's a different issue.  And not "changing" it, just the notion of
also having a mail server address.  Using a second domain name, just for
it, makes it easy should you, at some time, decide to have your mail
handled by a different machine than whatever handles your webserver.

Whatever domain name you use for your mail, whether that be
mail.pilotalk.com or just pilotalk.com, you should have a MX record for
it in your domain records.

How MX records are used:  Someone tries to send a message to
test-person@xxxxxxxxxxxx, their mailserver looks up the MX record for
pilotalk.com to find out how to reach your SMTP mailserver.  Their
mailserver connects to the MX record's address to deliver the mail.  If
it can't do so, it tries to send to the next MX record address.  And
walks down the list of MX record addresses until it can.  When it finds
one that accepts mail, it sends, and that backup mail server will
eventually pass the mail onto your mail server, as soon as it can.

You have no MX record.  Systems presume that they can use pilotalk.com
as the SMTP server, that may or may not be the case.  If your server is
down, you cannot get mail.  And people cannot even try to send you mail.

-- 
[tim@bigblack ~]$ uname -ipr
2.6.22.1-27.fc7 i686 i386

Using FC 4, 5, 6 & 7, plus CentOS 5.  Today, it's FC7.

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.




[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux