Something wrong with my hostname

C

-Cor-

Verified User
Joined
Sep 10, 2007
Messages
5
Hello everyone,

I'm running my own nameservers for over 2 years now, but recently experienced some random disconnects, which I think are connected to the hostname becoming improperly configured. So i'm trying for hours now to get the commands traceroute and host to display the proper hostname for my servers ip address. My hostname is masterchief.insension.net, but it keeps on nagging me by saying its insension.net:

Code: 
$sudo tracert 91.192.37.202
traceroute to 91.192.37.202 (91.192.37.202), 30 hops max, 60 byte packets
 1  my.router (192.168.1.1)  0.455 ms  4.536 ms  4.645 ms
 2  lb1.C10K05.nikhef.asd.xenosite.net (62.212.134.1)  11.951 ms  12.270 ms  12.506 ms
 3  gw4.ge-3-2-0.nikhef.asd.xenosite.net (62.212.131.22)  14.325 ms  14.567 ms  15.113 ms
 4  openpeering.nikhef.nl-ix.net (193.239.116.17)  17.824 ms  18.284 ms  18.525 ms
 5  openpeering.nikhef.cj2.nl (213.207.5.3)  22.330 ms  23.209 ms  24.368 ms
 6  rtr2-sig.ptp-3.cj2.nl (91.192.38.186)  24.770 ms  14.914 ms  15.454 ms
 7  insension.net (91.192.37.202)  16.149 ms  12.176 ms  12.954 ms

$host 91.192.37.202
202.37.192.91.in-addr.arpa domain name pointer insension.net.

When tracing the servers second ip (91.192.37.203) it correctly gives me masterchief.insension.net.

I tried everything i could think of: setting the hostname in DA via administrator settings -> Server's hostname, doing it manually via hostname.sh, setting the hostname via CentOS's 'setup' utility, setting it with the command 'hostname masterchief.insension.net' (just using hostname does return masterchief.insension.net correctly), adding the ip and hostname to /etc/hosts so it reads:

Code: 
# Do not remove the following line, or various programs
# that require network functionality will fail.
::1     localhost6.localdomain6 localhost6
91.192.37.202           masterchief.insension.net

In my desperation I even changed my resolv.conf to look like this:
Code: 
search insension.net
nameserver 91.192.37.202
nameserver 91.192.37.203
though I don't see how it would help me (ok, perhaps that's slightly stupid :))

Just to be complete, here are the dns records for the hostname in DA:

Code: 
ftp	A	91.192.37.202	
localhost	A	127.0.0.1	
mail	A	91.192.37.202	
masterchief.insension.net.	A	91.192.37.202	
pop	A	91.192.37.202	
smtp	A	91.192.37.202	
www	A	91.192.37.202	
masterchief.insension.net.	NS	ns1.insension.net.	
masterchief.insension.net.	NS	ns2.insension.net.	
mail	MX	10	
masterchief.insension.net.	TXT	"v=spf1 a mx ip4:91.192.37.202 ~all"

And this is how the records for insension.net look:

Code: 
ftp	A	91.192.37.202	
insension.net.	A	91.192.37.202	
localhost	A	127.0.0.1	
mail	A	91.192.37.202	
ns1	A	91.192.37.202	
ns2	A	91.192.37.203	
pop	A	91.192.37.202	
smtp	A	91.192.37.202	
www	A	91.192.37.202	
insension.net.	NS	ns1.insension.net.	
insension.net.	NS	ns2.insension.net.	
mail	MX	10	
insension.net.	TXT	"v=spf1 a mx ip4:91.192.37.202 ~all"

So now I hope someone can tell me how stupid I am, because I'm at a loss here as you can see.

Thanks in advance!
 
It shows me the correct hostname here. What exactly is nagging you?

Did you check /usr/local/directadmin/conf/directadmin.conf

Value servername= needs to match your server hostname. Directadmin program needs to be restarted as well after you change that.
 
Thanks for the reply!
Yes, I did set the servername in directadmin.conf to masterchief.insension.net, so nothing wrong there.

What is nagging me is why both host 91.192.37.202 and tracert 91.192.37.202 keep giving me insension.net as hostname instead of masterchief.insension.net while doing the same for 91.192.37.203 works correctly. It's giving me the impression that I configured something incorrectly.

Last night I tried a traceroute from Windows Vista instead of Ubuntu via the same connection as always and for some reason it returned masterchief.insension.net after flushing my DNS cache with ipconfig /flushdns

It gets stranger, because after rebooting into Ubuntu, it worked correctly there as well. This morning however, it just returned insension.net again, in stead of masterchief.insension.net

I think I'm slowly losing my mind... :)
 
It's dependent on your rDNS. It appears to be working correctly now.

Jeff
 
Thank you all!

It appears so indeed. The random disconnects were related to the fact that before posting this, my ns1 and ns2 had no A records (i forgot to add them after a nameserver change.... :S) Thank you all for taking the time to look into my problem though!
 
Last edited:
You must log in or register to reply here.
Back
Top