Issues with hostname/"fqdn" and post-install.

7 posts / 0 new
Last post
#1 Tue, 05/26/2009 - 10:48
packetloss451

Issues with hostname/"fqdn" and post-install.

I have been able to successfully install several times, however, I am not sure I am setting the hostname correctly before install.

I am currently setting vmin up on at VPS via the install script. Of course, the script works beautifully. The only hiccups have come from a hostname the script really couged on.

I have read and read. I just want to possibly clarify with those of you in 'the know'.

Let's assume I own the following domain name: iownit.com

My VPS control panel allows me to set the hostname for the system at any time...

What on God's green earth is the magic combo here? For example, I have set it at 'ev1.iownit' among others. I can't set it to anything longer (ev1.iownit.com) or yum DRAGS for days and the install script hurls.

If my main server domain is going to be 'www.iownit.com' ....what should my initial setup values be?

Tue, 05/26/2009 - 10:57
Joe
Joe's picture

If you want simple, just call it ns1.iownit.com (because Virtualmin defaults to using the hostname as the first NS record, so this saves you having to change that default).

If you don't like that idea, you'd go for something like primary.iownit.com.

You could also name it iownit.com, but you'll have to tweak the Postfix configuration a little later to make it happy about having iownit.com in the hostname and in the virtual maps file.

I think maybe you've got other problems, and you just think they're hostname related. Setting the hostname should not be an agonizing decision. It just a name, you know?

<div class='quote'>I can't set it to anything longer (ev1.iownit.com) or yum DRAGS for days and the install script hurls</div>

That makes no sense. Why would yum care about a long domain name? This makes me think you have intermittent DNS or network issues that you're attributing the the one thing you're agonizing over and attributing all problems to. ;-)

--

Check out the forum guidelines!

Tue, 05/26/2009 - 12:19 (Reply to #2)
packetloss451

I found my problem (I think). My server is a VPS running CentOS 5.3 under OpenVZ. My VPS control panel allows you to set the hostname. However, if you set the name in the form of 'ns1.iownit.com'--at first everything seems fine. However, after entering password to SSH into server...it lags for a VERY long time. It is under this scenario where the yum lags happen as well. Pretty much anything that requires the the server to make a request via network.

I can set the hostname from control panel to 'ns1.iownit' and all is fine.

I am stumped. I have done some searching and am pretty much stumped on configuring it manually via shell.

Tue, 05/26/2009 - 13:55 (Reply to #3)
andreychek

Hmm, is your DNS setup correctly on it?

What is in /etc/resolv.conf?

And if you log into your server, and type:

time host google.com

What result do you get? It should occur quickly, within milliseconds.
-Eric

Wed, 05/27/2009 - 03:50 (Reply to #4)
packetloss451

time host google.com returns:

<div class='quote'>real 0m0.001s
user 0m0.000s
sys 0m0.000s</div>

I have tried it with hostname in both forms and it doesn't vary.

Initially, resolv.conf contained

<div class='quote'>nameserver 64.79.200.111
nameserver 64.79.200.113</div>

I edited to make it:
<div class='quote'>domain elitevs.com
nameserver 64.79.200.111
nameserver 64.79.200.113</div>

The nameservers are the defaults added to my VPS provider's CentOS 5.3 LAMP template. elitevs.com is my actual domain and the one I am trying to make the primary server domain.

<div class='quote'>Why would yum care about a long domain name?</div>

It wouldn't. I agree that it is a DNS issue, however, I am not quite sure where the lag is coming from. It only happens when I set my hostname to ns1.elitevs.com via my VPS control panel or via hostname command in shell.

Bottomline: I am still experiencing the crawling pace if I adjust domain name in the form of xxx.yyyyy.zzzz

I am stumped.

Wed, 05/27/2009 - 07:11 (Reply to #5)
ronald
ronald's picture

<div class='quote'>domain elitevs.com
nameserver 64.79.200.111
nameserver 64.79.200.113</div>

you'll need nameserver 127.0.0.1 as well in there.
do you have more than (or at least) 256 ram on the vps?

should you just fill in ns1 instead of ns1.elitevs.com in the control panel?

Wed, 05/27/2009 - 07:42 (Reply to #6)
packetloss451

I have 512 of ram.
I added 127.0.0.1 and nothing changes.

*shrug*

Topic locked