connectivity check

Is the server behind a NAT router/firewall? Consumer-level routers, in particular, often are unable to actually route...they can't deal with traffic from inside the network coming back into the network on the public IP.

I'm not actually sure what this particular error means, though. I'm guessing it's one of the tests where our server makes a request of yours and expects a specific response, and in this case, got something else. This could indicate a misconfigured NAT or DMZ setting in the router, or something altogether different.

First up, your DNS is misconfigured at your registrar, unless you aren't hosting your own DNS (in which case, you'd want to disable DNS in Virtualmin, so it's not expecting DNS to be pointing to your server). We don't have any control over that, and it's not something you can fix in Virtualmin...you need to fix it at your registrar.

The website error is probably because of the registrar misconfiguration. Bad hostname means a lookup of that name fails.

Pings not working could be any number of things. Many consumer-level routers don't forward pings, or have to be explicitly configured to do so (or they may respond to pings themselves, rather than forwarding, when in a DMZ or NAT configuration). That IP address is a RoadRunner address, so I'm going to guess you are behind some sort of Linksys or Netgear or Belkin or whatever router that is doing NAT, and maybe you have the DMZ configured? This would definitely fall into the category of "consumer router", and so it's not going to behave appropriately in some situations. Pings may simply not work with that configuration, and there may be nothing to be done about it. That said, port 80 is not responding, at all, on that address, so if Apache is running then it's probably a misconfiguration in your router.

I think you're looking for problems in the wrong place: The Virtualmin server is probably not responsible for any of the problems you're seeing (though Sendmail being running is weird and maybe a little worrisome). DNS isn't working because your registrar is serving out name servers that don't know about your domain, and networking isn't working because your router isn't doing whatever it is that needs to be done to get traffic from the world to your server. (I'm guessing. More troubleshooting is needed to isolate the network problems. Like, can you get a response back from the server by hitting its private IP address?)

1st off, I have 5 Static IP's, 4 of which go directly from the Cable Modem to the Server, IP 202-205 No Router involved. I do have a Router, but I only have 1 IP going to the Router ip 206. My main Network for my office. all on DHCP through the Netgear Router. But my Server is stand alone. it doesn't connect to the Router at all.

OK, it's a matter of figuring out why the server isn't responding.

What does the ifconfig command print out on your server?

And, route -n?

The last few steps of the traceroute to your 74.87.143.202 address look like this:

5 ge-7-0-0.pr0.sea20.tbone.rr.com (66.109.9.77) 1.859 ms 1.904 ms 1.950 ms 6 ae-1-0.cr0.sea20.tbone.rr.com (66.109.6.144) 1.996 ms 1.573 ms 0.666 ms 7 so-1-0-0.cralid-rtr1.natnow.rr.com (66.109.6.87) 8.205 ms 8.187 ms 8.249 ms 8 gig1-11-1.cralid-bb11.natnow.rr.com (65.28.216.2) 9.612 ms 9.872 ms 10.092 ms 9 * * *

Which means it's either never making it to your server, or your server is not responding the the ICMP query.

nmap shows it down as well, so it's not just ICMP messages that aren't working...look like nothing is responding. So, either that IP isn't up on the server, a firewall is blocking it, or your ISP isn't routing traffic to that address.

I guess I just not sure on how to set up a DNS server, to get it working. Or If I can just use the DNS from Roadrunner, or if I have to use the DNS from the Host for the Domain Names are registered.

Virtualmin handles the DNS server side of things. You shouldn't need to do anything to your DNS server, it's all automatic.

The error you're seeing does not indicate a problem with the DNS server. It indicates that your domain registrar is serving out name servers that are not your Virtualmin server...and thus the DNS that Virtualmin is configuring for you simply isn't doing anything--no one knows to ask your server for DNS information. The registrar distributes your name server information to the world via the root name servers, people query the root name servers, and once they know who to ask, they send a request to the name server provided by the root server. In your case, the root servers are telling the world that your name servers are:

Name Server: DNS1.NAMERESOLVERS.COM Name Server: DNS2.NAMERESOLVERS.COM Name Server: DNS3.NAMERESOLVERS.COM Name Server: DNS4.NAMERESOLVERS.COM

They now appear to be responding appropriately, at least for www.asrservice.com. The MX record looks a little suspicious with forward100.nameresolvers.com as the mail server for your zone (which is fine, if that's what you intend and you want to forward mail through nameresolvers.com).

Again, if you want to use DNS service that is not running on your Virtualmin server, you should disable DNS service for that domain (click Edit Virtual Server for that domain, and then in "Enabled features" uncheck DNS and save it). If you do want to let Virtualmin manage your DNS, you would need to change the name servers at your registrar to point to the Virtualmin system. Disabling DNS on the server, will make this error during configuration and connection checks go away, because it won't be trying to resolve your hostname on the local box.

I don't know that RoadRunner provides DNS service. Even if they do, I'm certain they are not the people you want managing your DNS. But, right now, your DNS is handled by nameresolvers.com (which redirects to namejuice.com). Any DNS problems you have will have to be dealt with using their interface or whatever means they provide for editing DNS records.

So, some interesting stuff shakes out from that.

ifconfig indicates you have four physical ethernet ports on the server. Is that right?

Are all of them plugged in? It looks like just one of them is, when I try to ping your various IP addresses (203 responds to ping).

My spidey sense is telling me that you turned on routing within your kernel in the past, in a non-permanent way, and then the reboot turned it back off (since it's not on, by default). This would kill all of the ports that are not directly plugged in.

Two options in that case...turn routing back on (and this time do it permanently), or move those addresses onto a single physical interface (there's no reason to divide them up across a bunch of interfaces if you want them all facing the world).

Turning routing back on will probably get you back to where you were before the system was rebooted.

To do that browse to:

Webmin->Networking->Network Configuration->Routing and Gateways

Set "Act as router?" to Yes, save it, and apply configuration.

This will probably get those other addresses responding. You'll still have an odd and unnecessarily complex configuration (a server doesn't usually need to act as a router), but it will probably be working.

I'm going to go ahead and send this response, since I think it's all that's keeping your system from working as it was before. And then I'll post another reply about DNS, as it's a much deeper subject.

OK, DNS...where to begin?

You're missing one of the steps I described above in my discussion about DNS.

There's your DNS server, which is running your Virtualmin system. We can test that, since we now know that 203 is up and running, so I did:

-bash-3.2$ host asrservice.com 74.87.143.203 Using domain server: Name: 74.87.143.203 Address: 74.87.143.203#53 Aliases:

asrservice.com has address 74.87.143.202 asrservice.com mail is handled by 5 mail.asrservice.com.

Bam! Working DNS server! Virtualmin did its job, and you don't have to think about your DNS server. As I said, Virtualmin is already managing your DNS server for you. You don't need a tutorial on setting up a DNS server, because it's already setup and working fine.

However, the DNS server is not the only piece of the puzzle in providing DNS service.

Your registrar has to know about your DNS server in order for it to refer requests to your server. How you go about changing the name servers at your registrar is completely out of our control, and I'm wholly unfamiliar with namejuice.com. This is not something that happens on your server. No amount of configuring your DNS server will make this step happen.

Since you've indicated you're not afraid to read, I'll refer you to Jamie's introduction to the BIND DNS system section in the Webmin wiki:

http://doxfer.com/Webmin/BINDDNSServer#Introduction_to_the_Domain_Name

This will, hopefully, give you a reasonable mental map of how DNS works, and why things aren't working the way you think they are. There's also tons of BIND documentation there, but, as we've already established with testing, your DNS server is working fine. Nothing wrong with the configuration there, and you didn't do anything wrong. Virtualmin is managing your DNS zones without issue. Only thing missing is that the registrars are not pointing to your server, and you have to do that at the registrar not in Virtualmin.

I will offer a couple of tips:

When you configure a name server at your registrar it needs to be for a name that already resolves.

So, you need to create a couple of A (address) records at your current DNS server (nameresolvers.com) to point to your Virtualmin server IP. You'd want to create ns1.asrservice.com to point to 74.87.143.202 and ns2.asrservice.com to point to 74.87.143.203, for example.

Once those have propagated, and answering correctly, you can use those names as your nameservers at your registrar. That will start sending name server requests to your name server, instead of the ones at nameresolvers.com, and then you don't have to think about DNS anymore, because Virtualmin will handle.

Actually, I take that back, there is one other step required, since you didn't plan from the get-go to use Virtualmin to manage your DNS (or you perhaps did, but didn't realize all the intricacies of DNS). Virtualmin defaults to using the hostname of your server, whatever that might be, for the NS (name server) record on new DNS zones. This probably isn't ns1.asrservice.com, since you didn't plan for it to be your name server. So, you need to manually configure Virtualmin to use this name in NS records in the Virtualmin configuration. I'll just borrow for the docs for that step:

If, for some reason, you don't like the default name of the first NS record (taken from the hostname of your server), you can change it in the Server Template(s) that you use, in the BIND DNS domain section. The field is labeled Master DNS server hostname. Just like with the slave servers, this name must be valid and point to the correct IP address, otherwise name service will not work, or will be unreliable.

And, if you want to setup a DNS slave, you'd want to follow this: http://www.virtualmin.com/documentation/dns/slave-configuration

Wait, why are you changing your BIND configuration? I've already pointed out that your DNS server was working fine. There was nothing wrong with your DNS server. It was answering queries for your zones without trouble. I only referred to the documentation because you wanted to understand DNS better, not because I wanted you to go poking at your configuration.

The only change you need to make to DNS is at your registrar (namejuice.com). Nothing on your Virtualmin server needs changing (well, now it does, I guess...).

Do not format your server, please. We'll really be in for a long haul if you do that. ;-)

Pause for a moment, take a step back, and let's work through the problems on at a time.

I can login to your system and figure out what went wrong with you DNS server and put it back to rights, if you'd like. I can't do anything at your registrar, of course...you'll need to do that. See here for how to enable remote access using our Support module:

http://www.virtualmin.com/documentation/system/support

As I mentioned in my next to last reply, if this server was working in the past, merely enabling routing should have made everything start working again the way it was. Did you do that?