Server hostname not resolving from outside

[leafish_dylan]

Hullo all. Thanks for DA, it's a great program! I have some questions that I believe are related to DNS, but I'll apologise up front if this is the wrong place.

Here's the situation: we have a server that we want to host a load of sites on. Our server (host.network.com) was originally accessible by its name, but now is only accessible by IP. I'm not sure what I've broken!

I can ping the hostname from the server and get the right IP, (*.*.224.10) but pinging it from outside resolves to a different machine on our host's network (*.*.192.10).

Do I add our server's name as a domain name, or as an A record on the domain linked to the admin account? I've tried both with no success. Do I use our nameservers for this (I suspect this won't work), or the ones provided by the host?

All of the sites we're hosting are working great, but we want to have a place where we can run things like phpMyAdmin securely. At the moment we can access anything installed in /var/www/html by browsing to the IP address of the server, but we'd prefer to use the hostname.

Is it also possible to assign the server host name (host.network.com) to the admin account, too? We don't really want to use one of our business domains for this.

 

[leafish_dylan]

This isn't even possible without control over a higher-level nameserver, is it? Was it working previously because we initially had the host's nameservers set up in DA?

 

[nobaloney]

You need to put an A record for your hostname into the active authoritative zone file for that domain.

It doesn't matter where the zone file is hosted; that's where the record needs to be put.

For example, if your hostname is host.example.com, and the nameserver for the example.com domain is ns1.example.net, then you'd put an A record for host into the example.com zone file on ns1.example.net.

Jeff