Sponsored Content
Full Discussion: DNS Server with IPv6 support
Special Forums IP Networking DNS Server with IPv6 support Post 302123748 by skanatiker on Wednesday 27th of June 2007 04:10:40 AM
Old 06-27-2007
Thanks a lot for your answers so far.

Here is my output from the following command

netstat -ant -f inet6| grep "\.53":
Code:
tcp6       0      0  *.53                   *.*                    LISTEN
udp6    4142      0  *.53                   *.*

tcpdump is available on my machine. I have played around a bit with tcpdump, but i didn't find anything interesting in the output. Which parameters should i use to start tcpdump with?

In my named.conf i have set the listen-on-v6 directive to any.

And @porter: Thanks for the information. But i wasn't able to determine whether aix uses the parallel stack or unified stack approach. And if it uses the unified stack approach, where do i have to set the SO_REUSEADDR flag?


Another thing i'm not sure about is ip6.arpa zone. Do i need this zone at all? Does IPv6 not work without a correct ip6.arpa? It is only there for the reverse lookup, isn't it? so the dig request i had sent should also have been executed without the zone, or? Well, if i need it, how should it look like? I use one at the moment, and it is also loaded without any errors, but well, i'm not sure whether it is correct.

Are there any other zones that are necessary for IPv6 to work? So only the basic ones. I have a zone where my AAAA records are in.


I found out something very interesting now. When i execute "dig @::1 host1.v6mainzlab.com aaaa" the first time, i get an error in my bind.log. I have turned on logging in named.conf. The error is the following:

Code:
27-Jun-2007 10:24:03.450 general: error: client.c:1575: unexpected error:
27-Jun-2007 10:24:03.450 general: error: failed to get request's destination: failure
27-Jun-2007 10:24:08.458 general: error: client.c:1575: unexpected error:
27-Jun-2007 10:24:08.459 general: error: failed to get request's destination: failure

--------EDIT---------
I have played around a bit and tried to get the dns server started on another AIX 5.3 machine. There i have Bind 9.2.1 installed. It's the default package that comes with AIX 5.3. When i started bind i got an error message in the system log. He couldn't bind the IPv4 socket, because it is already in use. So, well, i think now we know, that AIX uses unified stack. Now i would have to know, where i have to set the flag SO_REUSEADDR. Just for testing i have set the dns not to listen on IPv4 by setting "listen-on port 53 {none};" in named.conf (btw - i did the same on the other machine with Bind 9.4.1 and it didn't work there).

On that machine, all my dig commands work fine now. I have changed /etc/resolv.conf to the following:
Code:
nameserver ::1
search v6.mainzlab.com

But when i want to ping host1 or host1.v6mainzlab.com the host cannot be found. Any ideas what is the problem here?

Last edited by skanatiker; 06-27-2007 at 06:18 AM.. Reason: set up dns on another machine
 

9 More Discussions You Might Find Interesting

1. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

2. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies

3. Solaris

NTP server to support IPv4 and IPv6 client

Hi I am looking to have an NTP server that will support both ipv4 and ipv6 clients. Is there anything specific about the configuration that I should be looking at? (7 Replies)
Discussion started by: eeisken
7 Replies

4. Solaris

checking Solaris 10 DNS server for IPv6

hi, i have a Solaris 10 DNS server, how do you check whether it can support IPv6 networking ? (0 Replies)
Discussion started by: Exposure
0 Replies

5. Solaris

IPv6 for Solaris DNS

I have Bind running on a Solaris box that is our main public DNS. Given my very limited knowledge on DNS, I changed a few of the zones in the DNS to be 'dual-stack'. I did it through Webmin, but I know that I can also do it by adding an AAAA-record to the zone file. My question is how can I make... (2 Replies)
Discussion started by: Dardeer
2 Replies

6. IP Networking

[ipv6_test] Kernel is not compiled with IPv6 support

Hello, i tried to enable IPv6 networking and after service network restart i seen these messages: FATAL: Error inserting ipv6 (/lib/modules/2.6.18-348.16.1.el5.028stab108.1/kernel/net/ipv6/ipv6.ko): Device or resource busy CRITICAL : Kernel is not compiled with IPv6 support Bringing up... (6 Replies)
Discussion started by: postcd
6 Replies

7. UNIX for Dummies Questions & Answers

Assigning ipv6 to bonding interface - getting old as well as changed ipv6 in ifconfig output

Hi, I have created a bonding bond1 interface with 6 Eth , mode=4. Recently i have changed my old ipv6 to new one and tried to restart as well as reload network service. Post which i can see old as well as changed ipv6 in ifconfig command output. Below are few files and command output for your... (1 Reply)
Discussion started by: omkar.jadhav
1 Replies

8. Solaris

DNS client added to DNS server but not working

Hi, We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies

9. UNIX for Beginners Questions & Answers

What determines DNS will query IPV6 address?

When I do simple nslookup it does not generate any query for IPV6 (AAAA). But sometimes I see DNS query for both A and AAAA are generated. What decides this? The reason I do not want AAAA query is in most of the cases AAAA records are absent. Hence, if one DNS server fails, the clients keeps... (1 Reply)
Discussion started by: broy32000
1 Replies
HOST(1) 							       BIND9								   HOST(1)

NAME
host - DNS lookup utility SYNOPSIS
host [-aCdlnrsTwv] [-c class] [-N ndots] [-R number] [-t type] [-W wait] [-m flag] [-4] [-6] {name} [server] DESCRIPTION
host is a simple utility for performing DNS lookups. It is normally used to convert names to IP addresses and vice versa. When no arguments or options are given, host prints a short summary of its command line arguments and options. name is the domain name that is to be looked up. It can also be a dotted-decimal IPv4 address or a colon-delimited IPv6 address, in which case host will by default perform a reverse lookup for that address. server is an optional argument which is either the name or IP address of the name server that host should query instead of the server or servers listed in /etc/resolv.conf. The -a (all) option is equivalent to setting the -v option and asking host to make a query of type ANY. When the -C option is used, host will attempt to display the SOA records for zone name from all the listed authoritative name servers for that zone. The list of name servers is defined by the NS records that are found for the zone. The -c option instructs to make a DNS query of class class. This can be used to lookup Hesiod or Chaosnet class resource records. The default class is IN (Internet). Verbose output is generated by host when the -d or -v option is used. The two options are equivalent. They have been provided for backwards compatibility. In previous versions, the -d option switched on debugging traces and -v enabled verbose output. List mode is selected by the -l option. This makes host perform a zone transfer for zone name. Transfer the zone printing out the NS, PTR and address records (A/AAAA). If combined with -a all records will be printed. The -i option specifies that reverse lookups of IPv6 addresses should use the IP6.INT domain as defined in RFC1886. The default is to use IP6.ARPA. The -N option sets the number of dots that have to be in name for it to be considered absolute. The default value is that defined using the ndots statement in /etc/resolv.conf, or 1 if no ndots statement is present. Names with fewer dots are interpreted as relative names and will be searched for in the domains listed in the search or domain directive in /etc/resolv.conf. The number of UDP retries for a lookup can be changed with the -R option. number indicates how many times host will repeat a query that does not get answered. The default number of retries is 1. If number is negative or zero, the number of retries will default to 1. Non-recursive queries can be made via the -r option. Setting this option clears the RD -- recursion desired -- bit in the query which host makes. This should mean that the name server receiving the query will not attempt to resolve name. The -r option enables host to mimic the behavior of a name server by making non-recursive queries and expecting to receive answers to those queries that are usually referrals to other name servers. By default, host uses UDP when making queries. The -T option makes it use a TCP connection when querying the name server. TCP will be automatically selected for queries that require it, such as zone transfer (AXFR) requests. The -4 option forces host to only use IPv4 query transport. The -6 option forces host to only use IPv6 query transport. The -t option is used to select the query type. type can be any recognized query type: CNAME, NS, SOA, SIG, KEY, AXFR, etc. When no query type is specified, host automatically selects an appropriate query type. By default, it looks for A, AAAA, and MX records, but if the -C option was given, queries will be made for SOA records, and if name is a dotted-decimal IPv4 address or colon-delimited IPv6 address, host will query for PTR records. If a query type of IXFR is chosen the starting serial number can be specified by appending an equal followed by the starting serial number (e.g. -t IXFR=12345678). The time to wait for a reply can be controlled through the -W and -w options. The -W option makes host wait for wait seconds. If wait is less than one, the wait interval is set to one second. When the -w option is used, host will effectively wait forever for a reply. The time to wait for a response will be set to the number of seconds given by the hardware's maximum value for an integer quantity. The -s option tells host not to send the query to the next nameserver if any server responds with a SERVFAIL response, which is the reverse of normal stub resolver behavior. The -m can be used to set the memory usage debugging flags record, usage and trace. IDN SUPPORT
If host has been built with IDN (internationalized domain name) support, it can accept and display non-ASCII domain names. host appropriately converts character encoding of domain name before sending a request to DNS server or displaying a reply from the server. If you'd like to turn off the IDN support for some reason, defines the IDN_DISABLE environment variable. The IDN support is disabled if the variable is set when host runs. FILES
/etc/resolv.conf SEE ALSO
dig(1), named(8). COPYRIGHT
Copyright (C) 2004, 2005, 2007-2009 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2000-2002 Internet Software Consortium. BIND9 Jun 30, 2000 HOST(1)
All times are GMT -4. The time now is 01:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy