Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : Find Server Name

[Fremont Servers]

Hello,

Does anyone know how to fix this error?

*** Can't find server name for address xx.xx.xx.xx: Server failed
*** Can't find server name for address xx.xx.xx.xx: Server failed
*** Default servers are not available

[billyjoe]

Yes, fix the DNS server that's responsible for the reverse zone for that IP address.

[Fremont Servers]

Hello,

Is it possible that the DNS on the server is not setup correctly.

I've talked to the person handling the DNS server, and it seemed everything is correct on his end.

Would it be possible to the the above error messages due to named?

[billyjoe]

Post specific IP addresses and I (or someone else) will be able to better diagnose your problem. Ensure that the DNS server itself has a reverse DNS entry. Make sure that the DNS server responsible for the reverse in-addr.arpa zone is configured properly.

[Fremont Servers]

The IP Address is 66.220.13.162.

This is the content in named.conf

-------
// $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.3 2001/05/28 13:47:00
sheldonh Exp $
//
// Refer to the named(8) man page for details. If you are ever going
// to setup a primary server, make sure you've understood the hairy
// details of how DNS is working. Even with simple mistakes, you can
// break connectivity for affected parties, or cause huge amount of
// useless Internet traffic.

options {
directory "/etc/namedb";

// In addition to the "forwarders" clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
// forward only;

// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
forwarders {
127.0.0.1;
};
*/
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;

/*
* If running in a sandbox, you may have to specify a different
* location for the dumpfile.
*/
// dump-file "s/named_dump.db";
};

// Note: the following will be supported in a future release.
/*
host { any; } {
topology {
127.0.0.0/8;
};
};
*/

// Setting up secondaries is way easier and the rough picture for this
// is explained below.
//
// If you enable a local name server, don't forget to enter 127.0.0.1
// into your /etc/resolv.conf so this server will be queried first.
// Also, make sure to enable it in /etc/rc.conf.
zone "gdznet.com" in {
type master;
file "db.gdznet";
};

zone "subnet160.13.220.66.in-addr.arpa" in {
type master;
file "db.13.220.66";
};

zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT"
{
type master;
file "localhost.rev";
};

// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example secondary config entries. It can be convenient to become
// a secondary at least for the zone where your own domain is in. Ask
// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is the first bytes of the respective IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to setup a primary zone, better make sure you fully
// understand how DNS and BIND works, however. There are sometimes
// unobvious pitfalls. Setting up a secondary is comparably simpler.
//
// NB: Don't blindly enable the examples below. :-) Use actual names
// and addresses instead.
//
// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf).
// The directory containing the secondary zones must be write accessible
// to bind. The following sequence is suggested:
//
// mkdir /etc/namedb/s
// chown bind:bind /etc/namedb/s
// chmod 750 /etc/namedb/s

/*
zone "domain.com" {
type slave;
file "s/domain.com.bak";
masters {
192.168.1.1;
};
};

zone "0.168.192.in-addr.arpa" {
type slave;
file "s/0.168.192.in-addr.arpa.bak";
masters {
192.168.1.1;
};
};
*/
------------

[billyjoe]

[forrest@almighty forrest]$ host -t NS 13.220.66.in-addr.arpa
13.220.66.in-addr.arpa. name server NS2.HE.NET.
13.220.66.in-addr.arpa. name server NS3.HE.NET.
13.220.66.in-addr.arpa. name server NS1.HE.NET.

[forrest@almighty forrest]$ host -t NS subnet160.13.220.66.in-addr.arpa
subnet160.13.220.66.in-addr.arpa. name server ns1.gdznet.com.
subnet160.13.220.66.in-addr.arpa. name server ns2.gdznet.com.


It appears that the reverse zone has been properly delegated by HE.NET out to ns1.gdznet.com and ns2.gdznet.com. So delegation isn't the problem.



The problem is with those 2 DNS servers (ns1 and NS2.gdznet.com)

[forrest@almighty forrest]$ telnet ns1.gdznet.com 53
Trying 66.220.13.162...
telnet: connect to address 66.220.13.162: Connection refused

[forrest@almighty forrest]$ telnet ns2.gdznet.com 53
Trying 66.220.13.163...
telnet: connect to address 66.220.13.163: Connection refused


Basically NAMED is not configured properly because it's not responding on port 53 like it should be.

[Fremont Servers]

BillyJoe,

What exactly should I put in named.conf to fix this problem?

[billyjoe]

Are you positive that named is even running? Do a netstat -an and post the output from all the lines that say LISTENING.

[Fremont Servers]

The output to "netstat -an" ...


Active UNIX domain sockets
Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr
bfc00000 (null) -669135248 -669135448 d777a300 0 0 0

[billyjoe]

Oops, I didn't notice that you're on FreeBSD. I don't have a FreeBSD machine in front of me, so I can't remember the correct command line switches to get the output I'm looking for. Basically I'm looking for a netstat output that lists all ports on all IP addresses that are in LISTEN state.

[Fremont Servers]

Named has been restarted.

nameserver is running now and listen on port 53

[Fremont Servers]

Originally posted by billyjoe
[forrest@almighty forrest]$ host -t NS 13.220.66.in-addr.arpa
13.220.66.in-addr.arpa. name server NS2.HE.NET.
13.220.66.in-addr.arpa. name server NS3.HE.NET.
13.220.66.in-addr.arpa. name server NS1.HE.NET.

[forrest@almighty forrest]$ host -t NS subnet160.13.220.66.in-addr.arpa
subnet160.13.220.66.in-addr.arpa. name server ns1.gdznet.com.
subnet160.13.220.66.in-addr.arpa. name server ns2.gdznet.com.

I'm not sure why reverse is not working.


If everything is correct, then new lookups directed against the server should resolve the ip to a name.

Do you know what is the problem?