Need help with making nameservers, They just won't want to work.

[rjd22]

ok I'm trying to make my own name servers on my registar and DA now they just don't want to work so I'm going to leave my question here.

I have 2 nameservers

domain: adapthosting.com
n1: ns1.adapthosting.com --> 87.98.218.205
n2: ns2.adapthosting.com --> 87.98.221.55

I registered this domain at domainsite.com

at domainsite I made 3 records:
A phoenix.adapthosting.com 87.98.218.205 300
A ns1.adapthosting.com 87.98.218.205 300
A ns2.adapthosting.com 87.98.221.55 300

I also registered them as nameservers since this needs to be done at domainsite.

now at DA i did all what was in this tutorial(the nameserver part):
http://www.directadmin.com/newinstall.html

Now they still don't work. Could someone explain to me what I'm forgetting?

 

[floyd]

What evidence do you have that its not working? You have not given us anything to check your nameservers with. adapthosting.com is not pointed to your nameservers so we cannot use that as a test domain. What domains do you have pointed to ns1.adapthosting.com and ns2.adapthosting.com?

 

[rjd22]

I pointed scriptfreakz.net to it

 

[floyd]

What does the log show when you try to start named?

 

[nobaloney]

It appears that either your nameserver daemon isn't running or that port 53 isn't open on your firewall. Port 53 needs to be open for UDP as well as for TCP/IP, in both directions.

Jeff

 

[rjd22]

I disabled the IP tables so it shouldn't be the firewall. Jeff how can I check both those things since named it running.

This is what the log shows:

zone 0.in-addr.arpa/IN: NS '0.in-addr.arpa' has no address records (A or AAAA)
zone 0.in-addr.arpa/IN: loaded serial 0
zone 1.0.0.127.in-addr.arpa/IN: NS '1.0.0.127.in-addr.arpa' has no address records (A or AAAA)
zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
zone 1.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.arpa/IN: NS '1.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.arpa' has no address records (A or AAAA)
zone 1.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.arpa/IN: loaded serial 0
zone adapthosting.com/IN: loaded serial 2008071001
zone phoenix.adapthosting.com/IN: loaded serial 2008071000
zone localhost.localdomain/IN: loaded serial 0
zone localhost/IN: loaded serial 0
zone scriptfreakz.net/IN: loaded serial 2008071000
running
zone scriptfreakz.net/IN: sending notifies (serial 2008071000)
zone phoenix.adapthosting.com/IN: sending notifies (serial 2008071000)
zone adapthosting.com/IN: sending notifies (serial 2008071001)

 

[floyd]

So named is running. Your problem is not there. Either there is a firewall somewhere blocking port 53 or named is not listening in the ip addresses you specified. Sometimes named is only listening on localhost.

netstat -npa

Look for things listening on port 53 and see if the ip addresses are listed with port 53 as well.

 

[rjd22]

tcp        0      0 0.0.0.0:993                 0.0.0.0:*                   LISTEN      14519/pop3-login
tcp        0      0 0.0.0.0:995                 0.0.0.0:*                   LISTEN      14519/pop3-login
tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN      3737/mysqld
tcp        0      0 0.0.0.0:587                 0.0.0.0:*                   LISTEN      29882/exim
tcp        0      0 0.0.0.0:110                 0.0.0.0:*                   LISTEN      14519/pop3-login
tcp        0      0 0.0.0.0:2222                0.0.0.0:*                   LISTEN      12894/directadmin
tcp        0      0 0.0.0.0:143                 0.0.0.0:*                   LISTEN      18892/imap-login
tcp        0      0 0.0.0.0:80                  0.0.0.0:*                   LISTEN      17843/httpd
tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN      20424/named
tcp        0      0 0.0.0.0:21                  0.0.0.0:*                   LISTEN      19709/proftpd: (acc
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      21791/sshd
tcp        0      0 127.0.0.1:953               0.0.0.0:*                   LISTEN      20424/named
tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN      29882/exim
tcp        0      0 0.0.0.0:443                 0.0.0.0:*                   LISTEN      17843/httpd
tcp        0      0 87.98.218.205:80            85.149.12.60:1938           TIME_WAIT   -
tcp        0      0 87.98.218.205:80            85.149.12.60:1917           TIME_WAIT   -
tcp        0     52 87.98.218.205:22            85.149.12.60:1937           ESTABLISHED 25879/0
tcp        0      0 87.98.218.205:80            85.149.12.60:1947           FIN_WAIT2   -
udp        0      0 0.0.0.0:14593               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:63106               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:31500               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:40478               0.0.0.0:*                               2582/avahi-daemon:
udp        0      0 0.0.0.0:20782               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:38964               0.0.0.0:*                               20424/named
udp        0      0 127.0.0.1:53                0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:10167               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:3397                0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:62795               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:62288               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:9555                0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:43864               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:11610               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:25435               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:47964               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:5353                0.0.0.0:*                               2582/avahi-daemon:
udp        0      0 0.0.0.0:53869               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:58105               0.0.0.0:*                               20424/named
udp        0      0 0.0.0.0:38527               0.0.0.0:*                               20424/named

 

[floyd]

As you can see only the loopback (127.0.0.1) is listening on port 53. Look at your named.conf file. You probably have something like:

listen on {
127.0.0.1;
};

Either delete it or add your ip addresses.

 

[rjd22]

ok looks like it recieves now but it denies the domain :S

client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 194.134.13.36#43278: query 'www.scriptfreakz.net/A/IN' denied
client 194.134.13.36#26957: query 'www.scriptfreakz.net/A/IN' denied
client 194.134.13.36#45905: query 'www.scriptfreakz.net/A/IN' denied
client 194.134.13.36#22688: query 'www.scriptfreakz.net/A/IN' denied
client 194.134.13.36#58436: query 'www.scriptfreakz.net/A/IN' denied
client 194.134.13.36#37737: query 'www.scriptfreakz.net/A/IN' denied
client 194.134.13.36#63745: query 'www.scriptfreakz.net/A/IN' denied
client 194.134.13.36#38259: query 'www.scriptfreakz.net/A/IN' denied
client 194.134.13.36#9164: query 'www.scriptfreakz.net/A/IN' denied
client 194.134.13.36#25220: query 'www.scriptfreakz.net/A/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied
client 88.191.14.196#57431: query (cache) '217.126.50.213.in-addr.arpa/PTR/IN' denied

this is prolly the last thing I need to overcome

 

[rjd22]

Ok I got them working now fter some googling. I will write a full tutorial on this so noone will have problems anymore

 

[technimad]

Hi, how did you solve this?
We're seeing the same problems here....

 

[technimad]

The problem here was:
directadmin updates /etc/named.conf and named uses /etc/bind/named.conf as it's configuration file.
created a hard link between these files and the problem vanished.

 

[scsi]

I would think there would be some sort of setting in the directadmin config file for this.

 

[floyd]

I do not have /etc/bind/named.conf at all

 

[nobaloney]

technimad and floyd are most likely using different OS Distributions.

I believe DirectAdmin does properly set up whatever is necessary to use the configuration file on all OS Distributions it uses. technimad, what OS Distribution are you using?

Jeff