DNS Errors

[Lisa Burrows-Collins]

Hi Lou,

Thank you for this info. It gives me a better understanding of IPv6.

Here is the output of my dig

; <<>> DiG 9.3.2 <<>> amazon.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3723
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 8, ADDITIONAL: 2

;; QUESTION SECTION:
;amazon.com.                    IN      A

;; ANSWER SECTION:
amazon.com.             60      IN      A       72.21.206.5
amazon.com.             60      IN      A       207.171.166.102
amazon.com.             60      IN      A       207.171.175.29

;; AUTHORITY SECTION:
amazon.com.             86400   IN      NS      pdns1.ultradns.net.
amazon.com.             86400   IN      NS      pdns2.ultradns.net.
amazon.com.             86400   IN      NS      pdns3.ultradns.org.
amazon.com.             86400   IN      NS      pdns4.ultradns.org.
amazon.com.             86400   IN      NS      pdns5.ultradns.info.
amazon.com.             86400   IN      NS      pdns6.ultradns.co.uk.
amazon.com.             86400   IN      NS      udns1.ultradns.net.
amazon.com.             86400   IN      NS      udns2.ultradns.net.

;; ADDITIONAL SECTION:
udns1.ultradns.net.     172800  IN      A       204.69.234.1
udns2.ultradns.net.     172800  IN      A       204.74.101.1

;; Query time: 648 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jan 18 09:03:40 2006
;; MSG SIZE  rcvd: 319



The same dig for amazon.com on a Linux 9 server running Bind 9.2.1-16 
returned the same response in 34 msec vs 648 msec show above.

Lou Goddard wrote:

>This is what you're looking for:
>
>"The listen-on-v6 option is used to specify the ports on which the
>server will listen for incoming queries sent using IPv6.
>The server does not bind a separate socket to each IPv6 interface
>address as it does for IPv4. Instead, it always listens on the IPv6
>wildcard address.
>Therefore, the only values allowed for the address_match_list argument
>to the listen-on-v6 statement are { any; } And { none;}
>Multiple listen-on-v6 options can be used to listen on multiple ports:
>To make the server not listen on any IPv6 address, use
>listen-on-v6 { none; };
>If no listen-on-v6 statement is specified, the server will not listen on
>any IPv6 address."
>
>Keep in mind that disabling ipv6 does not disable the ability to serve
>AAAA records.
>
>Compiling:
>Simply untar; ./configure; make; make install.  I don't know where bind
>is located on Enterprise 4.  You may have to manually update the system
>binaries.
>
>Slow resolution:
>Could you post a dig of the query?
>
>
>
>-----Original Message-----
>From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
>Behalf Of Lisa Burrows-Collins
>Sent: Friday, January 13, 2006 9:56 AM
>To: bind-users at isc.org
>Subject: DNS Errors
>
>Hello,
>
>I've set up DNS on our Linux Enterprise 4 server. It will resolve names,
>
>but slowly. When I run Ethereal to capture the DNS UDP packets, I see 
>that I receive a lot of
>
>"Standard query response, Format Error"
>
>in the Ethereal capture. This seems to be associated with the AAAA 
>lookups . Can I turn off IPV6 in Bind version 9.2.4.
>
>My other alternative I was looking at is upgrading to 9.3. However I 
>can't find an RPM for 9.3. I downloaded the bind-9.3.2.tar.gz file but 
>due to a lack of experience with compiling, I'm having problems doing an
>
>install from this download.
>
>I had DNS working just fine under Enterprise 3. I could really use some 
>advice on the DNS service under Enterprise 4.
>
>Thanks,
>Lisa Collins
>
>
>
>
>
>
>  
>

-- 
Thank you,
Lisa Collins
NEOMIN-System Analyst II
330.847.6464  Ext 1511