> -----Original Message----- > From: redhat-list-admin@xxxxxxxxxx > [mailto:redhat-list-admin@xxxxxxxxxx] On Behalf Of Ben Yau > Sent: Tuesday, January 20, 2004 12:44 PM > To: redhat-list@xxxxxxxxxx > Subject: RE: pop won't authenticate my password > > > Wow ... > this thread has just blown into something gargantuan hasn't it? :D > > Ed (first Ed), you might want to give us some history about > mccorduck.ws so we can understand the bigger picture. Hi Ben, Sure, I'd be glad to. Maybe that's the problem, I haven't been prolix enough and haven't supplied enough detailed information throughout this thread. ;-) And > also let us know what it is you want to do. For example: > > 1) where/how did you register the name? > 2) is the company you registered the name with going to house > your primary DNS? Or is that something you wnated to do on > your machine ? If the answer is that you don't know, that's > fine. We might be able to answer from knowing the answer to #1 I'll answer both 1) and 2) together along with the history. I originally purchased the rights to the domain name mccorduck.ws from Register.com (and boy, did they suck me in, but that's another story). They were hosting both my www.McCorduck.ws Web site and my @mccorduck.ws e-mail (through which I could receive and send). Then for some reason they transferred the administration of my domain name registration to a company called WorldSite.ws. The latter also hosted my Web site and my @mccorduck.ws e-mail account (through a WebMail interface) with no problems for several months. Then I got the cojones to install Red Hat Linux 9 as the sole OS on an older computer that was being replaced and, with a fixed IP address (24.24.15.155) supplied to me by my ISP for my home network and finding out that RH9 included both HTTP (Apache) and e-mail server software, decided to make my Linux box my Web site and e-mail host, much as at my work my office Windows computer has its own fixed IP and domain name and I use *that* also to host a Web and an e-mail server. (I guess it's all just a control thing.) WorldSite.ws has an online form where I could change my DNS association, so I did so, associating mccorduck.ws with the fixed IP provided by my ISP. Then I set up my Web server and site on my Linux box and thought I was good to go, but I couldn't get to the site either through http://(www.)McCorduck.ws nor through http://24.24.15.155. So I contacted WorldSite.ws' tech support, and this is what they said in reply: >Good Morning Ed, > > Your have your domain pointing to a nameserver named > the same as your > domain, mccorduck.ws. However, mccorduck.ws does not > respond. It appears > you have not configured a machine named mccorduck.ws to > serve as a > nameserver. Are you intending to run your own nameserver? > > Kindest Regards, > > The .WS Support Team Before I could answer, though, the very next day I noticed that typing in http://McCorduck.ws in any browser did get through to the Web site I had set up on my Linux box using Apache, and it's worked fine that way ever since. One down, more to go. I also noticed after I had changed my DNS with WorldSite.ws, I had stopped receiving any mail to my @mccorduck.ws address, and any mail I sent out never got delivered. I never contacted them about this issue until yesterday, thinking that once I got my e-mail problems resolved on my RH9 box, which is why I started this thread in the first place, I wouldn't have to bother them about that. > 3) did you want to serve the mail from your own machine? (and > house the incoming mail of mccorduck.ws on your own machine?) > > >From all the emails, it seems the answer to 3) would be yes. Yes, that's right. > It looks like network solutions whois only recognizes that > the domain is taken but it doesn't seem like there is any > name server entries set up. On nslookup from my machine it > recognizes that there is a mccorduck.ws. address > (24.24.15.155) and the NS record points back to itself. So > my guess is that you have only just registered your name and > somehow managed to get an address record in there and that's > it. This means that mccordck.ws. has not been set up to > recognize mail seriving or DNS serving. > > The NS record I had from nslookup for your domian (from my > work PC) was: > > mccorduck.ws. IN NS mccorduck.ws. > > anyway, what this means is : > > To serve and read mail from your machine you'd need to > 1a) register your machine mccorduck.ws. as a valid nameserver OR > 1b) find someone to be your primary nameserver (there are a > lot of companies who will do this, including possibly the > company you registered your domain > with) > > If 1a) and not 1b), then > 2) run a nameserver (most likely BIND) on your machine > > > Finally, you also need to: > 3) Include an MX record for your domain to point to your machine. > 4) then run sendmail (which it seems you are doing) to accept > mail as mccorduck.ws. (Cw definition) 5)then run pop3 so you > can access the email (this is surprisingly the easiest part) > > It seems like only step 5 is finished and step 4 is half-way > finished (sendmail is running, not sure if it will accept as > mccorduck.ws.). And it also seems like steps 1 through 3 > have not been attempted yet. > > Let me know if this sounds correct. Sorry for the confusing > style of my post. Hopefully it makes sense. > > > Ben Yau No, Ben, it makes a lot of sense, thanks so much. Regarding this part and based on what I said above about how I apparently got WorldSite.ws to open up access to my Web site just by asking, should I go back to them and tell them what you said, i.e. "This means that mccordck.ws. has not been set up to recognize mail seriving or DNS serving," and ask them to do this, too? I'll wait for your reply to this before I try any of your other steps. Ed McCorduck Department of English State University of New York College at Cortland ed@xxxxxxxxxxxxxxxxxxxxxx http://mccorduck.cortland.edu http://McCorduck.ws -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
