ispCP - Board - Support
BIND NOT RESOLVING HOSTNAME - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: System Setup & Installation (/forum-32.html)
+--- Thread: BIND NOT RESOLVING HOSTNAME (/thread-6578.html)

BIND NOT RESOLVING HOSTNAME - Somel - 05-01-2009 01:09 AM

Hi Guys,

Bind9 Query...

I have installed ispcp... several times now... and i'm starting to thinking in move to another control panel. However yestarday i give it another chance. Everything seems ok except a problem with DNS.

The service is running on my main address and is detected by ispcp, when you add a domain, zones are created. However bind9 seems even internally (127.0.0.1) not to resolve the new zones.

eth0= xxx.xxx.xxx.43
eth0:0= xxx.xxx.xxx.61

Code:
telnet xxx.xxx.xxx.43 53
Trying xxx.xxx.xxx.43...
Connected to xxx.xxx.xxx.43.
Escape character is '^]'.

Code:
telnet xxx.xxx.xxx 53
Trying xxx.xxx.xxx.61...
Connected to xxx.xxx.xxx.61.
Escape character is '^]'.

Code:
# nslookup mydomainispcp.tld
;; Got SERVFAIL reply from 127.0.0.1, trying next server
;; Got SERVFAIL reply from xxx.xxx.xxx.43, trying next server
;; Got SERVFAIL reply from 127.0.0.1, trying next server
;; Got SERVFAIL reply from xxx.xxx.xxx.43, trying next server
Server:         xxx.xxx.xxx.61
Address:        xxx.xxx.xxx.61#53

** server can't find domainispcp.tld.mymaindomain.tld: SERVFAIL

Named.conf

Code:
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
        type hint;
        file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
        type master;
        file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
        type master;
        file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
        type master;
        file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
        type master;
        file "/etc/bind/db.255";
};

include "/etc/bind/named.conf.local";
// bind Data BEGIN.

// dmn [mydomain.tld] cfg entry BEGIN.
zone "mydomain.tld" {
        type    master;
        file    "/var/cache/bind/mydomain.tld.db";
  notify  YES;
};
// dmn [mydomain.tld] cfg entry END.

// dmn [domainispcp.tld] cfg entry BEGIN.
zone "domainispcp.tld" {
        type    master;
        file    "/var/cache/bind/domainispcp.tld.db";
        notify  YES;
};
// dmn [domainispcp.tld] cfg entry END.

// dmn [{DMN_NAME}] cfg entry BEGIN.
// dmn [{DMN_NAME}] cfg entry END.

any Ideias???

Kid Regards, somel[/i]

RE: BIND NOT RESOLVING HOSTNAME - robbo007 - 05-06-2009 12:26 AM

Did you check in /var/cache/bind to see if your .db file for that domain was created and is correctly configured with your external IP address? Bind uses your external IP and not your internal. I'm a beginner and just solved some bind issues on my server. Brain Melting stuff...

Rob

RE: BIND NOT RESOLVING HOSTNAME - kilburn - 05-06-2009 12:41 AM

1: Do not use all-uppercase subjects on posts, it is really disgusting.
2: We're sorry that you had a bad experience with this community maintained software. That said, we look forward for your help on making it better. Thanks.
3: Your named.conf shows zones for "mydomain.tld" and "domainispcp.tld", but nothing about "mymaindomain.tld" (which appears in the nslookup error). Please post the "xxxx.tld.db" files as they are, tell us which OS/Distro are you using and which fqdn you had chosen when installing ispcp.

RE: BIND NOT RESOLVING HOSTNAME - Somel - 05-06-2009 01:04 AM

Hi robbo007 the domain was created correctly in the correct places.

Killburn sorry for the caps.

I was able to solve the problem, it seems that bind needed to have itself pointed in resolv.conf

so my resolv.conf ended up like this:

Code:
Nameserver 127.0.0.1
Nameserver MY_publicIP
Nameserver DNS_ISP_SERVER