Can't see Linode

DNS config for the zone looks fine by me.

$ dig @ns1.pixelrepublic.com AXFR pixelrepublic.com

; <<>> DiG 9.2.5 <<>> @ns1.pixelrepublic.com AXFR pixelrepublic.com
; (1 server found)
;; global options:  printcmd
pixelrepublic.com.      14400   IN      SOA     ns1.pixelrepublic.com. pcameron.kvb.edu.au. 2005061001 14400 7200 3600000 86400
pixelrepublic.com.      14400   IN      MX      0 pixelrepublic.com.
pixelrepublic.com.      14400   IN      NS      ns1.pixelrepublic.com.
pixelrepublic.com.      14400   IN      NS      ns2.pixelrepublic.com.
pixelrepublic.com.      14400   IN      A       64.62.190.111
ftp.pixelrepublic.com.  14400   IN      A       64.62.190.111
localhost.pixelrepublic.com. 14400 IN   A       127.0.0.1
mail.pixelrepublic.com. 14400   IN      CNAME   pixelrepublic.com.
plato.pixelrepublic.com. 14400  IN      A       64.62.190.111
www.pixelrepublic.com.  14400   IN      CNAME   pixelrepublic.com.
plato.                  14400   IN      A       64.62.190.111
pixelrepublic.com.      14400   IN      SOA     ns1.pixelrepublic.com. pcameron.kvb.edu.au. 2005061001 14400 7200 3600000 86400
;; Query time: 734 msec
;; SERVER: 64.62.190.111#53(64.62.190.111)
;; WHEN: Wed Sep  7 10:13:34 2005
;; XFR size: 12 records

I see some minor wierdness. You have "plato" in the example as a complete top-level hostname, AND as a fully qualified host. See:

plato.                  14400   IN      A       64.62.190.111
plato.pixelrepublic.com. 14400  IN      A       64.62.190.111

This shouldn't break anything, since you have the correct one in there, though you'll probably see log entries for "out of zone data ignored" or some such.

Some lookups will fail because ns1 and ns2 aren't resolving properly. Their glue-records exist on the TLD servers, but not in your zone. You need to add these:

ns1.pixelrepublic.com.  172800  IN      A       64.62.190.111
ns2.pixelrepublic.com.  172800  IN      A       64.62.190.112

I'm not sure if this is breaking anything, but the fact that your own zone isn't serving up the IPs for the nameserver hostnames is rather broken.

I'd use shorter TTLs though. 172800 (2 days) and 86400 (1 day), though "standard" are a long time to wait when you have things you need to fix like this. 14400 (4 hours) like your other hostnames isn't bad.

Thanks I added those lines, but there is another problem.

Each time I reboot the linode it reverts to the default host name.

Can I stop it doing this?

@dingolingo:

Each time I reboot the linode it reverts to the default host name.

Can I stop it doing this?
Have you put your hostname into the /etc/hostname file yet?

I tried this but it still reverted

Does the file /etc/conf.d/hostname exist?

Neither /etc/conf.d/hostname or /etc/conf.d exist

I'm running CentOS 3.5 with CPanel installed.

/etc/sysconfig/network

-Chris

The file reads:

NETWORKING=yes

HOSTNAME=localhost.localdomain

Sorry for my ignorance here but do append, or replace, the current HOSTNAME value?

You'll want to set HOSTNAME to whatever your host and domain name are. Like so:

HOSTNAME=plato.pixelrepublic.com

However, by default, each Linode acquires its primary (eth0) IP address via DHCP, and that might be overriding your hostname. You'll need to move off using DHCP and use a static configuration. Fairly easiy to do…

Edit /etc/sysconfig/network-scripts/ifcfg-eth0 to have values like so:

DEVICE=eth0
BOOTPROTO=static
BROADCAST=64.62.190.255
IPADDR=64.62.190.111
NETMASK=255.255.255.0
NETWORK=64.62.190.0
ONBOOT=yes

You'll also need a GATEWAY line in /etc/sysconfig/network:

NETWORKING=yes
HOSTNAME=plato.pixelrepublic.com
GATEWAY=64.62.190.1

That's assuming your IP is 64.62.190.111.

Either reboot, or log into your console via Lish and restart networking (/etc/init.d/network restart) to get those changes.

-Chris

@caker:

You'll also need a GATEWAY line in /etc/sysconfig/network

Actually, comparing my RH init scripts to my CentOS box, the CentOS box has the GATEWAY entry in the ifcfg-eth0 file. Either might work, but if not, move that GATEWAY line into the ifcfg-eth0 file.

-Chris

Many thanks, but I've run into several issues so decided to reinstall.

Once again many thanks for your input.

use debian

That was nice and helpful.