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


STOP! | 17 comments | Create New Account
Click here to return to the 'STOP!' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
STOP!
Authored by: Anonymous on Dec 12, '02 12:23:17PM

if you want still to use Rendezvous, choose an other local domain extension!

like .home or .myself ...

.local is reserved for Rendezvous usage, and you'll be sorry is it stop's working someday.



[ Reply to This | # ]
another solution
Authored by: matx on Dec 12, '02 08:14:50PM

our entire network is based on this .local thing.

it's not a good solution just to change everything we run to .home etc

the windows admins don't see it as a solution... ;)

10.2 was an unpleasant surprise in this area... no more name resolution... :(

SOLUTION:
we just changed our LOCAL entries
in /etc/resolver/local

to list our local name servers and changed port to 53

seems to work again...

:)

matx



[ Reply to This | # ]
another solution
Authored by: dlove on Dec 13, '02 07:21:08AM

That's excellent! I wish I'd known about it before I'd renamed our domain. Where'd you find out about /etc/resolver/*?

And for the record, yes, this does break Rendezvous. I don't personally consider that a loss, but YMMV. Proceed with caution. ;-)



[ Reply to This | # ]
another solution
Authored by: matx666 on Dec 13, '02 10:32:37AM

well, when 10.2 first came out and it broke our domain name resolution, we searched
hi and lo for a solution and found one on the apple discussion boards... someone had
figured this thing out (/etc/resolver/local). congrats to them. it works.

who needs rendezvous, not yet anyway.



[ Reply to This | # ]
another solution
Authored by: bluehz on Dec 13, '02 01:32:04PM

Yes where did you find out about resolver? I never heard anything about it. Just checked mine and its says:

nameserver 224.0.0.251
port 5353
timeout 1

I don't know WHAT the heck that is....none of my info...



[ Reply to This | # ]
another solution
Authored by: dlove on Dec 16, '02 01:46:25PM

That's Rendezvous' "Multicast DNS" information. Fortunately MDNS uses standard DNS queries, so replacing that info with your DNS server's ip and port 53 results in standard DNS queries being issued for the .local domain.

I tried dropping a foo.local file in that directory to see if subdomains would then resolve correctly, but it appears .local always gets processed first.



[ Reply to This | # ]