off topic - Mixing unicast and multicast DNS with .local

Not applicable

Hi all,

I have started seeing dns issues with some of our mac clients which have
started getting dns name MachineName.local when it should be
MachineName.uk-group.net

Users with this issue now have to enter network creds when accessing some
network drives. Where as before they would go straight in.
If i do klist on a problem machine there is a kerberos ticket.

Any help would be much appreciated

Myron

3 REPLIES 3

Matt
Valued Contributor

We have the same issues here. It appears to be more of a political issue than infrastructure issue with us though.

--
Matt Lee
FNG Sr. IT Analyst / Desktop Architecture Team / Apple S.M.E / JAMF Casper Administrator
Fox Networks Group
matthew.lee at fox.com<mailto:matthew.lee at fox.com>

Need Help? Call the Help Desk at (310) 969-HELP (ext 24357) or online at http://itteam<http://itteam/>
Help Desk Hours: Mon-Fri, 6AM-6PM PST

sean
Valued Contributor

This would most likely imply that there is something wrong with your DNS set up, but check the clients that are incorrect with the following:

[mac75:~] sholden% scutil --get HostName HostName: not set [mac75:~] sholden% scutil --get ComputerName mac75 [mac75:~] sholden% scutil --get LocalHostName mac75

ComputerName The user-friendly name for the system. LocalHostName The local (Bonjour) host name. HostName The name associated with hostname(1) and gethostname(3).

HostName doesn't need to be set, but you could set this to match you DNS name, which may prevent your issue, but isn't fixing the issue.

The 'hostname' command however, will show you the machine name including the domain.

[mac75:~] sholden% hostname mac75.ldn.framestore.com [mac75:~] sholden% sscutil --dns DNS configuration

resolver #1 search domain[0] : ldn.framestore.com search domain[1] : framestore.com search domain[2] : nyc.framestore.com search domain[3] : ice.framestore.com nameserver[0] : 172.16.81.3 nameserver[1] : 172.16.81.4 nameserver[2] : 172.16.17.4 order : 200000

This should be reflected in /etc/resolv.conf. For point of reference, if you were to boot a Mac with no connection, then 'hosthame ' would report

mac75.local,

however, if you were then to connect the network, it should then update itself once the connection was made to reflect the network it is now connected to

mac75.ldn.framestore.com

There is an article on Bonjour/Rendezvous, but this is really about conflicting with internal networks that also end .local and you have .uk-group.net

http://support.apple.com/kb/HT3473

and as suggested in the article, if you are running 10.6 and your DNS is configured correctly, everything should work.

I guess it would be useful for others on the list to know how you get your DNS name, are you running DHCP, if so what OS is serving them, etc?

Just for info, we have host files that provide a name against the ethernet address and then use these files with DHCP on Linux servers. DHCP is also supplying our domain searches and DNS Servers to our clients. We haven't seen what you describe.

Sean

sean
Valued Contributor

This would most likely imply that there is something wrong with your DNS set up, but check the clients that are incorrect with the following:

[mac75:~] sholden% scutil --get HostName HostName: not set [mac75:~] sholden% scutil --get ComputerName mac75 [mac75:~] sholden% scutil --get LocalHostName mac75

ComputerName The user-friendly name for the system. LocalHostName The local (Bonjour) host name. HostName The name associated with hostname(1) and gethostname(3).

HostName doesn't need to be set, but you could set this to match you DNS name, which may prevent your issue, but isn't fixing the issue.

The 'hostname' command however, will show you the machine name including the domain.

[mac75:~] sholden% hostname mac75.ldn.framestore.com [mac75:~] sholden% sscutil --dns DNS configuration

resolver #1 search domain[0] : ldn.framestore.com search domain[1] : framestore.com search domain[2] : nyc.framestore.com search domain[3] : ice.framestore.com nameserver[0] : 172.16.81.3 nameserver[1] : 172.16.81.4 nameserver[2] : 172.16.17.4 order : 200000

This should be reflected in /etc/resolv.conf. For point of reference, if you were to boot a Mac with no connection, then 'hosthame ' would report

mac75.local,

however, if you were then to connect the network, it should then update itself once the connection was made to reflect the network it is now connected to

mac75.ldn.framestore.com

There is an article on Bonjour/Rendezvous, but this is really about conflicting with internal networks that also end .local and you have .uk-group.net

http://support.apple.com/kb/HT3473

and as suggested in the article, if you are running 10.6 and your DNS is configured correctly, everything should work.

I guess it would be useful for others on the list to know how you get your DNS name, are you running DHCP, if so what OS is serving them, etc?

Just for info, we have host files that provide a name against the ethernet address and then use these files with DHCP on Linux servers. DHCP is also supplying our domain searches and DNS Servers to our clients. We haven't seen what you describe.

Sean