Search Again:

Re: dns problem resolution?

From: Men & Mice Support
Date: Thursday, November 4, 2004
Time: 2:33:26 pm

Explicit instructions for compiling version 9.3.0 are included in the
other message thread. If you need more help than that, feel free to
contact me off-list.

Chris Buxton
Men & Mice - Making DNS Easy
Customer Service and Sales Engineer

At 1:58 PM -0800 11/4/04, Jody McAlister wrote:
>I have version 9.2.3. I see other threads on how to upgrade so I'll
>read those. But I'm a unix newbie so compiling and such is out of
>my league.
>On Nov 4, 2004, at 11:42 AM, Men & Mice Support wrote:
>
>>What version of named do you have? Apparently, this option is only
>>available with version 9.3.0 and later.
>>
>>You can find out your version with this command:
>>
>>named -v
>>
>>Chris Buxton
>>Men & Mice - Making DNS Easy
>>Customer Service and Sales Engineer
>>
>>At 10:35 AM -0800 11/4/04, Jody McAlister wrote:
>>>I've tried this on two seperate machines , (10.3.2 & 10.3.5) and
>>>QDNS 4.6.1. It kills bind everytime I put the -4 in the Params
>>>setting as instructed below. As soon as I remove it, all starts
>>>up just fine.
>>>
>>>
>>>On Nov 1, 2004, at 1:51 PM, Men & Mice Support wrote:
>>>
>>>>We're working along these same lines, but initial tests have not
>>>>been uniformly positive.
>>>>
>>>>If you want to try this as described, a few changes will be
>>>>required to work within the framework provided by QuickDNS. I'm
>>>>going to assume you're using QuickDNS 4.6.1, since if you're
>>>>using an earlier version either you need to update (for free if
>>>>you're using version 4.5 or later), or you're probably not having
>>>>this problem (since you're using BIND 8).
>>>>
>>>>Instead of modifying /System/Library/StartupItems/BIND/BIND,
>>>>you'll need to modify /Library/StartupItems/QuickDNS/named. Look
>>>>for a line like this, near the top:
>>>>
>>>>PARAMS=""
>>>>
>>>>Add -4 inside the quotes, like this:
>>>>
>>>>PARAMS="-4"
>>>>
>>>>This takes care of settings for both starting and restarting. To
>>>>activate it, simply execute this (with root privileges):
>>>>
>>>>/Library/StartupItems/QuickDNS/named restart
>>>>
>>>>Chris Buxton
>>>>Men & Mice - Making DNS Easy
>>>>Customer Service and Sales Engineer
>>>>
>>>>At 2:18 PM -0800 11/1/04, Jody McAlister wrote:
>>>>>The mac os x server list just posted this message regarding dns
>>>>>lookups. they've been basically having the same thread that we
>>>>>had last week.
>>>>>
>>>>>I haven't tried it yet. I'm posting so maybe men and mice can
>>>>>confirm before I start playing with my server.
>>>>>
>>>>>*********************************************************************************************************************
>>>>>(Copied message begins here...)
>>>>>
>>>>>A more complex, but more reliable fix MacFixIt reader Ken has
>>>>>discovered a clever workaround that involves modifying the
>>>>>operation of Mac OS X's "named" daemon -- the DNS server that is
>>>>>part of the BIND set of UNIX DNS utilities.
>>>>>
>>>>> The theory behind why this fix works is as follows: root domain
>>>>>servers appear to have recently been given IPv6 capability, and
>>>>>are now returning AAAA records in response to name lookups.
>>>>>
>>>>> Ken writes "The simple upshot is that for whatever reason, the
>>>>>first time named tries to go do a DNS query, it seems to decide
>>>>>to try sending to an IPV6 server address, which is pretty much
>>>>>guaranteed to fail for most users. Eventually this times out and
>>>>>it retries, but by that time Safari has usually given up on
>>>>>resolving the address and you get an error. The second time you
>>>>>try it, the correct address has already been cached by the
>>>>>system and everything works.
>>>>>"I found that a very simple fix (if you don't mind editing OS
>>>>>config files) was to modify the
>>>>>/System/Library/StartupItems/BIND/BIND file to add the '-4'
>>>>>option to named, which forces it to only use IPV4. For example,
>>>>>the first part of the file normally looks like this:
>>>>>
>>>>> StartService ()
>>>>> {
>>>>> if [ "${DNSSERVER:=-NO-}" = "-YES-" ]; then
>>>>> ConsoleMessage "Starting named"
>>>>> named
>>>>> fi
>>>>> }
>>>>>
>>>>>
>>>>>I changed the above to:
>>>>>
>>>>>StartService ()
>>>>> {
>>>>> if [ "${DNSSERVER:=-NO-}" = "-YES-" ]; then
>>>>> ConsoleMessage "Starting named"
>>>>> named -4
>>>>> fi
>>>>> }
>>>>>
>>>>>
>>>>>"You should probably do the same thing for the RestartService
>>>>>section in the file. You'll either need to restart named by hand
>>>>>with the new option, or simply reboot your system to have the
>>>>>above take effect (probably the safest thing to do). I haven't
>>>>>yet tried digging into the BIND code deeply enough to determine
>>>>>why it seems to favor IPV6 address over and over again even
>>>>>though it never gets a valid response. It appears as though
>>>>>there is some code within BIND to sort the servers on response
>>>>>time, but IPV6 servers seem to always wind up at the front of
>>>>>the list."


Messages In This Thread:


Return to Digital Point Solutions' Home Page

home
products
services
support
email lists
optigold isp
optigold isp news
home inspection
inspectrix
java companion
oracle
quickdns pro
search engine
veterinary
tips
employees
free tools
portfolio
jobs
contact

Sales:
888/4-DPOINT

Support:
858/452-3696


Search:
Add this to your site