> > > > 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 This is a great resonse from Worldsite.ws. btw. A major clue as to some of the things which are not working for you right now. You wouldn't be able to get to www.mccorduck.ws because there is no DNS entry. There is one DNS enry and that is mccorduck.ws and it's an A record so anyone wanting to talk to mccorduck.ws (via ftp, http, whatever) will go to your linux box . I am a bit puzzled though on why you were not able to access it directly via the IP. Perhaps your apache httpd.conf is configured to not accept requests with the IP in the address field. > > 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. > Possibly DNS propogation time. > 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. Because after the DNS propogated, there were no longer any MX entries in your DNS. Any machine attempting to send mail to @mccorduck.ws would not be able to find a mailhost for it. As far as sending mail out, that could be a number of reasons depending on how your sendmail is set up to relay. A possible cause is that the reverse lookup for your linux box is not working. Doing nslookup on mccorduck.ws resolves to the IP, but perhaps nslookup on the IP doesn't resolve back to mccorduck.ws. > > > > 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. > >From the sounds of it, right now you just want to host the website and the mail server. I agree that this is enough right now and you do not want to handle DNS on your machine. So contact worldsite.ws and let them know this is what you need from them: 1) worldsite.ws be the primary nameserver for mccorduck.ws and 2) Put these entries in for my domain mccorduck.ws. IN A 24.24.15.155 24.24.15.155 IN PTR mccorduck.ws. www.mccorduck.ws. IN CNAME mccorduck.ws. @ IN MX mccorduck.ws. The first is the one you already have The second is for reverse lookup(esp. since you are serving mail from this machine) THe third is so that www.mccorduck.ws will also go to your website The fourth is to recognize mccorduck.ws. machine (24.24.15.155) as the main mail relay for mccorduck.ws. Remember that you will have to wait up to 72 hours for DNS to propogate meaning you may not see the changes right away. Also, depending on how worldsite does its DNS changes, you may have to wait a little longer. There should be a written policy for this. For example, some ISP's have a written policy that all DNS change requests are not processed until 7pm that night (or something like that) so that they can do all the changes at one time. Ask worldsite.ws about this.. something like "WHen I make a request to modify or add DNS entries, when are they put in and how long will it take until I'm able to see it (or how long will it take to propogate?)". In addition, and on a whole different topic, since you are going to be putting this machien out there, you're also going to want to secure this machine down to protect from hackers. This means 1) Ask your ISP if they provide firewall services for the static IP address you have. IF asked, let them know that for now you want to allow only port 80 and port 25 (web and sendmail). If you also want to use POP3 from a machine outside your home to the machine inside your home, you wlil also want them to allow port 110. and/or 2) start reading on what iptables and ipchains do. Eventually youwill need to work with these to further secure your box, esp. if your ISP does not provide firewall services. That's a eyeful for sure. Good Luck Ben Yau -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
