Changed network domain name - minor problem

Soldato
Joined
20 Feb 2011
Posts
3,969
A wee while ago I finally learned that using local as my network domain name was inadvisable so I changed it to home.lan. This was done on my router, a UDM. My tablet and phone can access local resources using the new domain name no problem. However, my Mac will only connect to resources using the old .local name. The Search Domains in the network settings shows the home.lan domain so I'm a bit stumped as to how to fix this issue. Any help would be great!
 
I cannot offer any help but you may want to post it under the Apple software section.

People seem to post Mac qestions\issues under here


Hopefully you will get more help
 
Last edited:
not sure but possbily flush the DNS cache on the mac?


That was a good call as I'd completely forgotten about trying that. Unfortunately it didn't make any difference. I really thought it would!

I cannot offer any help but you may want to post it under the Apple software section.

People seem to post Mac qestions\issues under here


Hopefully you will get more help

Will do. I'm still not sure if it's a Mac issue or a network/ router problem but I'll pop into the Apple forum to see if anyone can advise.
 
Will do. I'm still not sure if it's a Mac issue or a network/ router problem but I'll pop into the Apple forum to see if anyone can advise.
To me it sounds like its something the Mac is holding on too as others have updated fine (I maybe wrong lol)
 
To me it sounds like its something the Mac is holding on too as others have updated fine (I maybe wrong lol)

It's definitely the Mac that's got the issue as I can access domain services from other clients including a MBP. No idea what's causing the problem. Might be a browser cache issue which I'll look into later.
 
Just bumping this thread as the issue is still outstanding despite my best efforts. I can't work out why the Mac will only access local domains on the old domain name - perhaps because it was .local? Has anyone come across this issue before?
 
Do you actually have a DNS server running on your network that is resolving these addresses? .local is what Bonjour uses for service discovery so that's the domain your Mac will be using.
 
Yes, I've got a UDM that resolves the addresses. This works for the various other Macs, tablets, phones and whatnot I have dotted around the house save for my Mac Studio. If I look at the DNS entry for the problem Mac the Search Domains are correct so it's been supplied with the correct form.
 
Does the correct address resolve if you go into Terminal and

dig hostname.lan @yourdnsserverIP
 
Last edited:
some googlefu produced:


Code:
Just put a file in /etc/resolver/ with a name such as "searchappend" with these contents:

search example.com

Just don't name the file "com" or some other valid TLD. This works because of OSX's resolver magic. For more info, read through the documentation on your mac with this command:

man 5 resolver

I have a file there called "consul" that looks like this:

nameserver 127.0.0.1
port 8600
search consul

That magically makes it so .consul is appended to the search path, and any resolving for .consul TLDs uses my local nameserver.

Also leads to the question, is your router handing out .local to dhcp requests for search suffix config?
 
Last edited:
Back
Top Bottom