 |  |
Scott, may I suggest you submit a report summary of your trials and
Re: Problems resolving (my case is similar)
From: Thomas Carpentier
Date: Friday, October 29, 2004
Time: 1:39:01 am
thoughts to macfixit? A lot of problems, when diagnostic is solid,
have seen a good reaction from Apple.
At 12:58 AM -0700 10/29/2004, Scott Haneda wrote:
>on 10/28/04 7:31 PM, Scott Haneda at lists@newgeo.com wrote:
>
>> on 10/28/04 4:44 PM, Men & Mice Support at cbuxton@menandmice.com wrote:
>>
>>> At 3:00 PM -0700 10/28/04, Scott Haneda wrote:
>>>> on 10/28/04 2:57 PM, Jody McAlister at jodymac@iscweb.com wrote:
>>>>
>>>>> Both of mine are QDNS 4.6.1 and secondary is 10.3.2 client and the
>>>>> primary is 10.3.5 client
>>>>
>>>> Can someone tell me how to fully remove QDNS and get BIND 9 up and running
>>>> so I can rule out QDNS as the culprit?
>>>
>>> It's not QuickDNS, since QuickDNS doesn't affect how the name server
>>> operates, but here it is for completeness.
>>
>> Apparently a few days ago AAAA records were added to the roots a few days
>> ago, and apparently, there is a long standing issue with the BSD's and IPv6,
>> that's all I have been told, maybe someone here knows more about this and
>> how to fix it now.
>
>Sorry to keep babbling on about this, its been 3 days of non stop trying to
>figure this out. I am convinced this is a bug in the core of OS X. I think
>it has something to do with IPv6 and not being able to turn it off. Even
>with it turned off, some posts I found on google lead me to believe that it
>still is on.
>
>I am not sure what this AAAA record is all about, but the recent change at
>the root servers to start using this mechanism seems to be the source of the
>trouble, though indirectly.
>
>If I enter in:
>nserver2.apple.com. 319383 IN A 17.254.0.59
>Into my tcp/ip settings, I also get the failure, these are apples's NS's, I
>have to imagine every apple employee on the web is currently having trouble
>resolving hostnames. Hopefully this gets apple to get a patch out soon. I
>suspect from what I have heard the trouble is in the BSD subsystem, so not
>sure how that patch works anyway.
>
>If there was some way to tell named to start in some legacy mode to not
>bother with these new AAAA records, that may prove to fix it, hopefully the
>men and mice folks know how to make that happen.
>
>If that does not do it, I guess it will be time for a 1U Linux server to
>take over the task of my DNS, though I sure would love to not have to go
>that road, never touched Linux before. In case I do have to go that road,
>can someone recommend a good 1U server for me, it will only run DNS, so
>whatever is most cost effective. Also, what flavor of Linux should I put on
>it?
>--
>-------------------------------------------------------------
>Scott Haneda Tel: 415.898.2602
><http://www.newgeo.com> Fax: 313.557.5052
><scott@newgeo.com> Novato, CA U.S.A.
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 |
888/4-DPOINTSupport:
858/452-3696