Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'DirectoryService high CPU utilization' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
DirectoryService high CPU utilization
Authored by: operator207 on Jul 19, '10 12:27:35PM

I fixed this type of problem by using BIND locally. I even have it setup to resolve certain domains using forwarders. (Helps when you have internal DNS at work, but still want to use your ad blocking setup)

null.zone.file:

$TTL 24h

@ IN SOA localhost. root.localhost. (
2010032301
86400
300
604800
3600)



@ IN NS localhost.
@ IN A 127.0.0.1
* IN A 127.0.0.1

blocked.zone.file:

zone "101com.com" { type master; notify no; file "null.zone.file"; };
zone "101order.com" { type master; notify no; file "null.zone.file"; };
etc...


Then point your DNS in Network Prefs to 127.0.0.1. If you want to query certain DNS servers for a particular domain, in your named.conf file add something like this:

zone "domain.net" IN {
type forward;
forward only;
forwarders {ip.of.dns.remote.server;};
};

I am sure there is more to it (installing BIND via Mac Ports/Fink, having it run as a service), but the above is the parts that allow you to use BIND as a ad blocker. Installing BIND is up to the user. So it securing BIND so you do not allow others to query your machine for DNS, unless you want to.

BTW, everything I have written in this post, I have gleamed in one way or another from MacOSXHints, and reading man files or docs for BIND.



[ Reply to This | # ]