Re: curious DNS behavior on a 7.0...
however, right now new every website i browse is penalized with a 10-20 second delay before the page finally starts loading. tcpdump is full of these: wouldn't it be your browser requesting the IPv6 address? you can check easy enough by pinging any website (which you haven't resolved yet) and see if u get the same calls. Good observation. unless you are pointing your resolver to localhost, and your local named is requesting the v6 records. Look into disabling this behaviour @ named.conf. I don't personally believe disabling this is the right approach. For instance, I set up a test IPv6 IP on an interface on a 100Mbps LANx WAN fast Ethernet connection. I then added an record to a named server. Working from another server on the same physical network (albeit different subnet across separate interfaces), the query time for both is exactly the same. Note that my resolver on 'cohiba' points to 208.70.104.3. cohiba# dig lanx-fa1.ibctech.ca lanx-fa1.ibctech.ca.7087IN 3ffe:ff00:1::1 ;; Query time: 0 msec cohiba# dig lanx-fa1.ibctech.ca ;lanx-fa1.ibctech.ca. IN A ;; Query time: 0 msec ...Now, performing the same test, from the same server, using the same DNS box looking for the exact same www site that the OP stated that was a problem originally: # INITIAL DNS LOOKUP cohiba# dig www.srh.noaa.gov ; DiG 9.3.2 www.srh.noaa.gov ;; ANSWER SECTION: www.srh.noaa.gov. 86400 IN A 216.38.80.20 ;; Query time: 210 msec ;; SERVER: 208.70.104.3#53(208.70.104.3) # SPECIFIC IPv6 LOOKUP (no answer) cohiba# dig www.srh.noaa.gov ; DiG 9.3.2 www.srh.noaa.gov ;www.srh.noaa.gov. IN ;; Query time: 102 msec CONCLUSION: If the last poster is right and it's only the browser is failing because it uses it's own faulty internal DNS resolver, then this is obviously a serious hindrance to the implementation of IPv6. Of course most 'users' aren't on the 'Internet' if their MSN page doesn't display, and will take the path of least cost to make it work ;) I'm not a protocol expert, but from what I can tell, a web browser DNS resolver/cache that works this way may also have quite an impact on the view regarding usability of any OS as IPv6 becomes more prevalent, not just FreeBSD. I've never noticed these problems before. Running Portable Firefox on my Windows XP workstation, I see the IPv6 and IPv4 address of all sites I go to, if they are v6 enabled. However, I have 16^N variables involved that make that an unfair evaluation. -- Does anyone else have issues in this regard? Particularly, does anyone else have IPv6 enabled, or better yet in use that can provide any feedback? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: curious DNS behavior on a 7.0...
Quoting Steve Bertrand [EMAIL PROTECTED]: CONCLUSION: If the last poster is right and it's only the browser is failing because it uses it's own faulty internal DNS resolver, then this is obviously a serious hindrance to the implementation of IPv6. so a browser behavior, and not an operating system or name server behavior? as far as i know, my name servers dont know how to speak ipv6 either, as they are 6.2p8's without INET6 in their kernel configs. so, my browser of choice is opera, but admittedly, i dont recall ever seeing a setting i can change concerning this behavior. how then, would one go about elminating ipv6 behavior from a browser? Of course most 'users' aren't on the 'Internet' if their MSN page doesn't display, and will take the path of least cost to make it work ;) not sure if that was intended for me or not... if so, my retort is if i wanted path of least cost (in terms of time and trouble)... i would have just got on my ibook which 'just works' (har har :) *shrug* all i know is that my other systems that have no ipv6 at all, arent able to produce such behavior. cheers, -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] This message was sent using IMP, the Internet Messaging Program. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: curious DNS behavior on a 7.0...
Jonathan, On Thu, 2007-11-01 at 20:41 -0500, Jonathan Horne wrote: [...snip...] however, right now new every website i browse is penalized with a 10-20 second delay ... [...snip...] Type about:config in the Firefox address bar. Then edit the following value: (default is false) network.dns.disableIPv6 That's enough to solve your problem ;; Sincerely, -- So if Jules doesn't marry you, you can be a rich old maid. -- Micahel Corleone, Chapter 27, page 384 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: curious DNS behavior on a 7.0...
Steve Bertrand wrote: -- Does anyone else have issues in this regard? Particularly, does anyone else have IPv6 enabled, or better yet in use that can provide any feedback? I have a couple of ideas. First, named has some flags like -4 and -6 (see man named). Second, firefox has a config flag to disable ipv6 lookups. Go to about:config and search for ipv6. For instance, mine shows network.dns.disableIPv6 user set boolean true -- Said one park ranger, 'There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists.' Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
curious DNS behavior on a 7.0...
reading the /etc/defaults/rc.conf, ipv6 appears disabled by default: ### IPv6 options: ### ipv6_enable=NO# Set to YES to set up for IPv6. however, right now new every website i browse is penalized with a 10-20 second delay before the page finally starts loading. tcpdump is full of these: 20:38:57.915695 IP athena.dfwlp.com.59056 castor.dfwlp.com.domain: 3505+ ? www.srh.noaa.gov. (34) arent 's ipv6 lookups? as i mentioned in another thread, i cant get the kernel to compile right now (thus eliminating the INET6 line), so im trying to figure another way out to stop this behavior). any ideas would be appreciated. cheers, -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: curious DNS behavior on a 7.0...
Jonathan Horne wrote: reading the /etc/defaults/rc.conf, ipv6 appears disabled by default: ### IPv6 options: ### ipv6_enable=NO# Set to YES to set up for IPv6. however, right now new every website i browse is penalized with a 10-20 second delay before the page finally starts loading. tcpdump is full of these: 20:38:57.915695 IP athena.dfwlp.com.59056 castor.dfwlp.com.domain: 3505+ ? www.srh.noaa.gov. (34) arent 's ipv6 lookups? as i mentioned in another thread, i cant get the kernel to compile right now (thus eliminating the INET6 line), so im trying to figure another way out to stop this behavior). It's not required you remove IPv6 from the kernel in order to receive proper DNS A record responses, and even if IPv6 name services take precedence, it shouldn't cause such a delay (unless all of your boxen/DNS servers point to the same forwarders that cause this issue). I have several machines under 4.10 to 6.2, and at least two running 7.0 that are v6 enabled that don't have this issue. I do run IPv6 in my network with a legitimate block, however, I do not have any IPv6 name servers that contain any outside DNSv6 records. That said, more particulars are needed to find out what is happening. The most important thing to know in order to break this down is what name server(s) are you using on this particular server to resolve names. If you can post the output from the following whilst logged into one of the problematic machines, it will likely help: # cat /etc/resolv.conf If your box is a DHCP client, I won't know what to look for in that output. If by chance your box attains it's IP information via DHCP, then the next following output (particularly the last few lines) will help: # dig www.srh.noaa.gov Your queries may or may not be detrimental to the time in which you receive your DNS responses. I would personally lean toward the latter, given the lack of information. Don't go about recompiling the kernel without v6 support yet. It seems DNS is timing out for you somewhere, so post the above requested info and it can go from there. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: curious DNS behavior on a 7.0...
On Thu, 1 Nov 2007 20:41:13 -0500
Jonathan Horne [EMAIL PROTECTED] wrote:
however, right now new every website i browse is penalized with a 10-20
second delay before the page finally starts loading. tcpdump is full of
these:
hi there,
wouldn't it be your browser requesting the IPv6 address? you can check easy
enough by pinging any website (which you haven't resolved yet) and see if u get
the same calls.
unless you are pointing your resolver to localhost, and your local named is
requesting the v6 records. Look into disabling this behaviour @ named.conf.
cheers,
B
_
{Beto|Norberto|Numard} Meijome
Anyone who isn't confused here doesn't really understand what's going on.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
