According to whois, the domain name servers responsible for mystyka.com are out of hostsave.com. Their nameservers are resolving your domain name to an address on their network. So your bind installation is mute to anyone not using your bind server as their dns. You need to change the dns servers listed with your registrar to show the ip address of your name server or you need to access the dns servers at hostsave.com and put entries in for your mail and www. machine etc.
Larry S. Brown Dimension Networks, Inc. (727) 723-8388 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wikked Skye Sent: Sunday, March 30, 2003 12:36 AM To: [EMAIL PROTECTED] Subject: RE: NameServer, DNS, and BIND I have done the dig thing, and it looked alright there. There is really nothing on the system at all right now, so I am fine giving out that information. When I do ping for the ip it comes back fine, but when I ping the domain name it comes back host unknown. I am indeed using the Apache Server. ip 64.91.118.88 I am able to hit the site with this. domain www.mystyka.com I get cannot be found/cannot resolve with this. nameservers ns1.mystyka.com and ns3.mystyka.com Those cannot be found either. Thanks. I am trying very hard to stay away from Microsoft's Windows Server and I know this is the right way, I just wish there was more documentation on it. I have not been real successful with finding much. Kelly -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
