Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Snow Leopard on Unsupported PowerPC Macs
- Thread starter Larsvonhier
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
IIRC back in my Mac OS X Server sysadmin days, there was bug in earlier 10.6.0-10.6.4(?) builds of OS X server where DNS lookups would just stop working. I remember having a ticket in with engineering at Apple because Open Directory looked itself up constantly behind the scenes, often breaking Kerberos for clients and corrupting Open Directory user accounts.
At the time, one of the workarounds was to run bind locally on the server to let it cache the DNS lookups, then use 127.0.0.1 as the name server for OS X Server.
For clients (we did this for a while for testing), you could compile and run dnsmasq (https://thekelleys.org.uk/dnsmasq/doc.html) locally. It's been several years, but I think we would run dnsmasq and point the system's DNS server to 127.0.0.1. This worked around the flaky DNS implementation on the early 10.6 builds.
I dug up an old thread mentioning what I recall doing: https://apple.stackexchange.com/questions/26616/dns-not-resolving-on-mac-os-x
I also recall (I think in 10.6) that when DNS lookups broke, using scutil was usually the command that you could play around with to get it intermittenty work.
I don't have a system readily available to test this with, but hopefully this info is worth a shot!
---
TLDR: There was a bug in early 10.6 GM releases related to DNS. What if you run a third party DNS server (dnsmasq) and point the system's DNS server to 127.0.01? Using a third party DNS server might work around the issues you're having making DNS queries, and pointing the system name server to 127.0.0.1 wouldn't require the DNS lookups to make an external request.
At the time, one of the workarounds was to run bind locally on the server to let it cache the DNS lookups, then use 127.0.0.1 as the name server for OS X Server.
For clients (we did this for a while for testing), you could compile and run dnsmasq (https://thekelleys.org.uk/dnsmasq/doc.html) locally. It's been several years, but I think we would run dnsmasq and point the system's DNS server to 127.0.0.1. This worked around the flaky DNS implementation on the early 10.6 builds.
I dug up an old thread mentioning what I recall doing: https://apple.stackexchange.com/questions/26616/dns-not-resolving-on-mac-os-x
I also recall (I think in 10.6) that when DNS lookups broke, using scutil was usually the command that you could play around with to get it intermittenty work.
I don't have a system readily available to test this with, but hopefully this info is worth a shot!
---
TLDR: There was a bug in early 10.6 GM releases related to DNS. What if you run a third party DNS server (dnsmasq) and point the system's DNS server to 127.0.01? Using a third party DNS server might work around the issues you're having making DNS queries, and pointing the system name server to 127.0.0.1 wouldn't require the DNS lookups to make an external request.
Last edited:
If you will build other ones, please upload. There are more binaries which lack ppc slices in 3.2.6, and that shows up. (Pulling over from 10a190 works, but is suboptimal, understandably.)