Named ipv6

Djunity

Verified User
Joined
Mar 9, 2008
Messages
243
Location
Holland
Hi all,

We got the following problem with named according to some posts on the forum if you comment out the following lines in /etc/named.conf
//listen-on port 53 { 127.0.0.1; };
//listen-on-v6 port 53 { ::1; };
(is commented out by default)
named should listen on all ip addresses on the server, it does for ipv4 but not for ipv6 bind aint listening on ipv6 adres als i look with nmap i get
Nmap scan report for 2001:1be8:3f03:480::2:2a0
Host is up (0.00046s latency).
Not shown: 994 closed ports
PORT STATE SERVICE
21/tcp open ftp
80/tcp open http
111/tcp open rpcbind
443/tcp open https
2222/tcp open unknown

Nmap done: 1 IP address (1 host up) scanned in 0.12 seconds
when i change the named.conf and set
listen-on-v6 port 53 { ::1; 2001:1be8:3f03:480::2:2a0;};
restart named then the result is
Starting Nmap 5.21 ( http://nmap.org ) at 2012-02-06 17:39 CET
Nmap scan report for 2001:1be8:3f03:480::2:2a0
Host is up (0.00046s latency).
Not shown: 994 closed ports
PORT STATE SERVICE
21/tcp open ftp
53/tcp open domain
80/tcp open http
111/tcp open rpcbind
443/tcp open https
2222/tcp open unknown

Nmap done: 1 IP address (1 host up) scanned in 0.12 seconds

So apperently named aint listning on the ipv6 by default.

Any one got an idea on how to fix this or is this in issue in da ?? this is a fresh install from about 2 weeks ago centos 6 64 bit
 
Netstat should tell you what ports and ips its listening on.
 
If there is in fact a DirectAdmin default configuration for named.conf (and note that I'm not disputing it), I've never seen it. I've used my own for years. From where are you installing BIND? From where does this default configuration come?

Thanks.

Jeff
 
Hi Jeff,

Im refering to the conf that is installed when you install a clean version of da so basic the clean version of bind conf to.

What im asking is that da by default add the above solution to get bind to listen on ipv6
 
Thanks for pointing that out, scsi.
Says right in it:
Code:
// a caching only nameserver config
so I'll stick with the one I wrote :).

If you want to use it note that while certain code has been removed and it no longer serves cached results by default, it doesn't allow transfer, and it doesn't notify slaves, so it's not really suitable in a real master-slave DNS configuration without changes.

Jeff
 
Back
Top