ARD 3.5.1 DNS NAMES

Hi,
All imacs run 3.5.1 and i'm seeing a lot of inconsistency in the DNS Name column. Here are some examples:
hostname.local
hostname.domain.com
and quite a few still have the dns name of the master image that was applied to the machine.
The computers all seem to function as they should, WGM settings are applied and they can log in ok.
Where does ARD get this DNS info from?
As DNS is controlled via a 2008 server, the computers still resolve to their correct DNS address.
Any ideas how to get ARD to resolve the correct DNS name?
TIA

This is a link to a previous thread with a similar problem. The solution by Scooter Magrooter of resetting the task server is the one that works best for me. Hope this helps you.
https://discussions.apple.com/message/16201614#16201614

Similar Messages

Where does ARD get it's DNS information from? Wrong DNS name reported.

It's very strange...ARD is reporting a DNS name for one of my servers that has long been removed from my network. I can't figure out where it's pulling this info from? The servers real DNS name is not being reported at all. I know the IP this new server has is a recycled IP from an earlier server that may have had that DNS name associated with it but that was literally three years ago. How do I change this? Whenever I try to rename it manually it just flips right back.

Hi Rab1967 ,
The first question :
The IP addresses are from host records .The name of the record is the domain name(In the zone ,the name is displayed as “ same as parent folder “ .) .
The second question :
When we type characters in nslookup ,it will query for host records by default .To see the settings of nslookup ,type
set all .
For detailed process of the query ,we can use debug mode of nslookup .
To enter debug mode ,type
nslookup and then type set d2 .
Here is the guide for using nslookup :
Nslookup :
https://technet.microsoft.com/en-us/library/cc940085.aspx
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

DNS names keep "flikkering" randomly in Apple Remote Desktop

Hi there,
Since the update to ARD 3.7 all my DNS names keep 'switching' randomly between the several Computers (14) i have in the network.
On site.. if you open ARD you see the DNS names changing every second or so.. to a random other name, which is also in the network. Often there are to the same DNS names (the computer name stays stable)
This wasn't the case in ARD 3.6.2.. and as a result .. is is now very hard to work with the machines via a remote VPN.. (it works but is is terrably slow)
any how i searched the net.. and one conclusion:
https://discussions.apple.com/thread/4190442
that nothing is wrong.. is not a good and correct answer in my opion..
because i have really seen working remote with ARD through a VPN tunnel (wich have not changed.. the only thing changed was ARD 3.7 and Maverick on most machines)
Any how.. i any one out there has any suggestion.. please let me know..
(its a 40 minute drive to the other place every time)
Greetz
CJ

Well, add my 50 computers to the list!
When I did the upgrade to ARD 3.7 on OS 10.8.5 all user names and passwords for those 50 computers were lost! Had to re-add them all one-by-one
... and after closing ARD the passwords were gone again Then I did a Permission Repair and at least this problem was fixed and the passwords "re-appeared" (I'm not sure whether this problem occured because I use a standard user account for work).
Anyway, later, I swapped the IP's of two OS X servers and modified their DNS entries accordingly. nslookup is properly resolving the names but ARD goes berserk with those two servers and always keeps using the wrong, 'historic' host names and/or IPs.
It has been annoying for quite a long time and many ARD versions that you could not override this stupid ARD name caching behaviour (or whatever it is) by manually editing the ARD clients host name/IP (hey, Apple, did you ever hear about "nslookup" or "dig"?). In ARD 3.6.2 it finally seemed to be fixed and now they re-introduced this buggy behaviour again!!!
If they are not able to program a query for the correct and current data, they should at least allow me to edit this information manually and permanently. This information must not be overwritten by any bizarre automatic mechansim using data that are completely out of date.
Does anybody know where the host name/IP information of the clients is stored and if it might be edited brute force? Or at least if there is a cache that can be emptied?
Hope this will be fixed soon and finally forever!

Prefer DNS name to last known IP

One of the most annoying behaviors of ARD is that is seems to care only about the IP of the client. I frequently lose connections to clients in our DHCP environment when the IP changes. ARD already knows the DNS name of the client, but it does not seem to even try to do a DNS lookup to try to reconnect when the IP changes. Does anyone know of a hack or other method to have ARD do a DNS lookup when it cannot contact a client?
Thanks!

Get Info on the client. Edit the info. Delete the IP address. You may, or may not, need to make an edit of some sort in the DNS field (so it registers a change). Save the new info.
This should force ARD to prefer the DNS name over the IP address.

Where does ARD get its "DNS Names" from?

I've been plagued with this for months now: Many of my ARD clients have bogus entries in the "DNS Name" column. Some of them are just previously used names (showing as "MacLab-02.local" when the computer is now named "MacLab-15", for example). And some of them are names that I have never actually assigned (showing as "maclab-124.local", when I've never used lower case or numbers that high).
No matter what I do, I can't seem to fix these. In the clients' Sharing prefpane, the correct .local name is showing. When I type "hostname" at the command line, the correct name shows. Using every method I've ever known to check the names, in fact, they'll show the right ones. Except in ARD.
So... where on earth is it picking up these names? How do I clear or fix that list?
Thanks!
john

That was never my intention (do some windows platform dependend registry stuff)
However i had a broken network entry in that specific part of the registry which chrashed my application. Now i can just delete it and my problem is gone :-)
Probably some uninstaller missed something or only partly removed it, or the entry was from some failed installation procedure - how knows?
Now it is working,
ToM
PS: Yeah some may point out (which is right) to do some good error checking/exception handling however since the app is already rolled out a proper bugfix needs time and this solution provides a quickfix to make it work instantly...

How to change DNS name ?

I have an iMac and Macbook Pro, both of which I set up to triple-boot Leopard, XP and Ubuntu. I've noticed that after booting into one of the other OSes, the DNS Name of that machine shown in Remote Desktop will remain whatever it was called in Ubuntu/XP even after rebooting into OS X.
On the iMac this seems to revert to normal after some time/number of reboots but the MBP insists on appearing as ubuntu.config in ARD and as ubuntu in my command line prompt in Terminal. This is especially annoying as I have since wiped the two extra partitions and returned to a single volume of OS X.
I know it's hardly a big deal but I've tried everything I can think of and I'd appreciate some advice.
Thanks

Well I have the correct hostname in Terminal now.
I tried the obvious things (SysPrefs->Sharing->Computer Name->Edit->Local Hostname). Rebooted, same old same old. I tried running sudo hostname <my choice>, rebooted, no change.
Finally I ran sudo nano /etc/hostconfig, added a line HOSTNAME=<my choice>, rebooted and my prompt was correct but Remote Desktop still showed ubuntu.config. My /etc also has a hostconfig~ so I added the HOSTNAME line to that and rebooted but Remote Desktop just refuses to recognise it.
I've had a poke round in every plist I can find that seems relevant but I'm all out of ideas.

Updating DNS Names

Hi Everyone - first post, so please bear with me whilst I learn the ettiquette here
I administer a classroom of about 30 macs (mainly G4 eMacs with about 10 power macs) for a postgraduate newspaper journalism class. We recently (last summer) decided to try to implement a more comprehensive management/imaging scheme for them, and bought apple remote desktop and a copy of Tiger Server.
The problem I'm currently having is updating the DNS name information in the Apple Remote Desktop application (server side). I've had all of the dns records for the machines updated to something human readable so that dns information can be used as part of an automatic renaming process on newly imaged machines. But ARD still displays the old names.
I've tried refreshing the dns cache on the server on which they're stored, as well as removing machines and re-adding them by IP address. Reverse DNS lookups (which is the method apple says ARD uses to set the DNS name when computers are added) work in any other context. But ARD still remembers the old, out of date DNS information.
Does anyone have any pointers as to what's going on? Where is this information cached, and how can it be updated?
Thanks in advance!

Hi Brian, thanks for replying.
I didn't enter the dns details for the machines in the first place. I can edit the dns names manually, but that isn't the point. The ARD manual does state fairly clearly that the DNS names are set when the machine is added using reverse-dns lookup. This should ensure that the DNS name setting is correct, and should safeguard against typos etc.
Of course, even if I were to re-type each DNS address manually (possible for 30 odd machines, I suppose, though it wouldn't be if this were 300 odd), I'd have to do a reverse dns address for each computer address ANYway.
I suppose I could bypass the problem by writing a hybrid applescript/bash script that looked up the dns address for a given IP address and changed the dns name through ARD... but I'd prefer it if there was a way to force ARD itself to re-lookup the information so that it was correct.

How to stop OS X from retrieving reverse DNS name ?!

Hello guys,
I have a small problem that's very annoying. I manage a couple dozen Macs at work via ARD. All Macs are up to date and so is ARD.
Recently i started to notice something bizzare in ARD, meaning that from time to time a couple of Macs that were passed over from an ex employee to another current employee, behaved erradic in ARD. Sometimes they appear offline, sometimes they dissaper entirely (also in Scanner), BUT most of the times they appear with incorrect DNS name (ex DNS name from the ex employee or even duplicates DNS names)
I attached a pic in which you can clearly see what i'm all about.
I tried different situations and config mods, and i almost nailed it when i changed the DHCP DNS settings from the router. Currently the router LAN DNS settings points to the local server (ie: 10.0.1.2) which has DNS enabled and then to the public DNS. If i switch the entires, then the DNS names appear correctly in ARD, but if i do that i also loose the iChat service which is dependent of that entry.
SO i think the best way is to figure out a way to stop OS X from retrieveing reverse DNS names. Is this possible?

I've have this issue too. This thread may be helpful:
https://discussions.apple.com/thread/4190442
Most of our computers have static IP addresses assigned, so it is just some laptops that receive DHCP that seem to get confused in ARD sometimes. As in your case, the computers themselves never have an issue - it is just ARD that gets mixed messages. It also never seems to affect ARD, it just displays incorrectly. While I'm not entirely convinced this is fixable, I took the advice of the thread above and when it gets really bad, I simply go to "All Computers" and delete everything out. Then I quit and reopen ARD and then from the Scanner, I re-add the computers and re-organize them. We only have about 30 computers, so it goes quick when they are all turned on. They seem to stay pretty organized for a while... and then the cycle begins again.

DNS Name not Sharing Name

Howdy all,
I've been noticing and have been dealing with until now that the entry in the DNS Name column doesn't always report accurate.
For example
I have a laptop/desktop named Comp-Mac28-UserName in the Sharing Preferences' Computer Name Field.
ARD reports in it's Name field the same from the Sharing Prefs' as above.
However in the DNS Name, I get one of either the :
• correct name
• Unknown
• blank (as in white space and not the word blank)
• another machine's name (oddly enough, a Windows machine)
Has anyone seen, dealt with this bug, annoyance or feature?
Thanks in advance.
-p

I believe this is due to the TTL (Time To Live) for DNS entries. We just moved over to VLans here and all the machines are grabbing new DHCP IP numbers. Because of this as new computers are moved over they are grabbing numbers of other systems that have been turned off for a while. The old DNS name still exists on that IP. Use Network Utility to see what DNS names are associated with that IP. I bet that more than one name is on that IP number.

DNS Name field empty - why?

Hi all,
Please forgive my naive question, I am not a guru of networking...
I am trying to understand why the Macs in my network (10.4.9) always have their DNS name field in ARD 3.1 empty ("Unknown") whereas the PCs (although obviously not accessible with ARD) do show up with their DNS name.
I can edit each computer "info" window, but I am not quite sure that's the way it should be done.
What do I have to do in order to know and see the DNS name?
Isn'it it supposed to be the (Mac) computer's name.local ?
Many thanks for your attention.
Cheers
Carlo
Powerbook 12 Mac OS X (10.4.9)
Powerbook 12 Mac OS X (10.3.9)
Powerbook 12 Mac OS X (10.3.9)
Powerbook 12 Mac OS X (10.3.9)

It sounds like your user account is not in the admin group. Open System Preferences -> Accounts and check that there is at least one admin account. If none of those accounts are listed as admin accounts, see here for a fix: http://discussions.apple.com/thread.jspa?threadID=1323191&tstart=0

Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."

Hi,
Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."
DC:windows Server 2008 R2
Domain functional level:Windows Server 2003
When Winxp join domain, have no this error message.
I checked http://support.microsoft.com/kb/2018583?wa=wsignin1.0 does't work.
There have 3 suggestion in this article:
1.The "Disable NetBIOS over TCP/IP" checkbox has been disabled in the IPv4 properties of the computer being joined.
Doesnt's work.
2.Connectivity over UDP port 137 is blocked between client and the helper DC servicing the join operation in the target domain.
On my DC, I run netstat -an, reslut as below:
UDP 192.168.20.3:137 *:*
3.The TCP/IPv4 protocol has been disabled so that the client being joined or the DC in the destination domain targeted by the LDAP BIND is running TCP/IPv6 only.
We are not using IPV6.
This server recently updated from Windows Server 2003 to Windows Server 2008 R2. Before upgrade, when Win7 and Win2008 join this domain, also have the same error message.
Please help to check this issue.
Thank you very much.
BR
Guo YingHui

Hi Guo Ying,
I have faced this critical error which makes over-writes the host names in the domain when you join.
For example: Already you had a host name called as PC.domain.com in the domain.com Domain.
When you try to add the another host name called as PC in the domain.com Domain, it doesn't give you the duplicate name error on the network it does over-write the existing host name called as PC.domain.com & it will add the new host name into the domain.
Host name which got over-written will get removed from the domain. I faced this issue in my project. My DPM host name got removed from the Domain & new host name got joined into the domain which halted my backups for one day.
Final Resolution is as follows:
You need to start the dns console on the DC & drop down the domain name.
Select the _msdcs when you click on _msdcs it will show the Name Server's list on the right hand side.
You need to add the Domain Naming Master under the _msdcs or add all the domain controllers which you had.
After you add the Name server's try joining the PC OR Laptop to the domain which is successfully joins it.
Regards
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

Rdp://full%20address=s: IP or DNS Name is not user friendly... Can rdp:// IP or DNS Name be assumed as the full address in Microsoft Remote Desktop?

We would like to request Microsoft Remote Desktop (MRD) to behave the same as the open source CoRD.app on OS X with respect URL resolution.
Example:MRD will resolve from Terminal rdp://full%20address=s:<IP or DNS Name>, but not rdp://<IP or DNS Name>
As the OS will respect any of the following protocols in Terminal or browser:
afp://<username>@<IP or DNS Name>
cifs://<username>@<IP or DNS Name>
ftp://<username>@<IP or DNS Name>
ftps://<username>@<IP or DNS Name>
http://<username>@<IP or DNS Name>
https://<username>@<IP or DNS Name>
smb://<username>@<IP or DNS Name>
ssh://<username>@<IP or DNS Name>
vnc://<username>@<IP or DNS Name>
(<username> can be omitted to force authentication at connection) it seems slightly redundant to force "full%20address=s:" in the URL.
Can Version 8.0.1.6 be modified address this request?
What is the proper way to report an enhancement request or bug?
Thank you for your consideration.

Hi,
From your description it appears that you want to modify the pattern for assigning the rdp full address but this doesn’t support as per your requirement. That is the default string which we need to have for passing full address.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

DNS Name in OD Password Server field?

So, I got a new juniper firewall the other day to reduce the amount of work my main server has. Fire it up, configure it, and I notice that password server requests are going out the NAT, then back into the public IP of the server.
My question is this: would it be wise and/or acceptable to change the IP address to a URL in OD (in WGM, Click on target, config in the popup, passwordserver in the list, value in question is PasswordServerLocation and dsAttrTypeNative:apple-password-server-location)?
I would rather do this as the internal DNS points the proper name to the internal IP, while the external does the same for the public IP, so password server would work properly no matter where a user is.

Hi,
johan wrote:
> Is it possible to put a DNS name in an Exception filter ?
No.
> And can i open a filter for a range of destination addresses like 10.0.6.*
Well, sure. You use a Network as destination (vs. a HOST).
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

Domain name/"primary DNS" name/mail host name/mail server name/mx name

Hi,
I have registered my domain name (N.com) with an external dns server and created an MX record (mail.N.com) for it as well. My server sits behind a router and internet traffic is port(80)-forwarded to my server's fixed internal ip address (I can access my webpages from the internet just fine). When I initially setup the server I was asked to give it a "primary DNS name." I naturally assumed that N.com was supposed to be entered here, but that just caused all kinds of problems (though I still do not understand why). So I reinstalled and currently have server.N.com as the primary DNS name of the server (although it shows up in Server Admin and Workgroup Manager as server.local--why is that?)
I have had no luck getting any email from the internet with the default settings in mail services (domain name of N.com and host name of server.N.com). Having no luck with the defaults, I assumed that maybe I needed to change the host name to "mail.N.com" so that it matched the MX record. I also changed the user preferences in Workgroup Manager to receive mail from mail.N.com--but still no luck. Could someone tell me what I am doing wrong and how come none of the Mail Service literature mentions anything about what a mail "host name" is supposed to be? Is it supposed to be the same as the "Mail Server" name that Workgroup Manager asks each user for? and is it the same as the MX record name?
I am just needing some help to connect all these variously named, but undefined, dots.
Also, how come I can access webmail from the internet using www.N.com/webmail but can't do it from any computers within my physical network (I have to use IPaddress/webmail or server.local/webmail)?
Also, should my user email addresses be [email protected] or [email protected] (which is the current default)?
Thanks in advance and good luck!
John

I had been told by a friend that ... regular email coming in from the internet would go through port 80
Unfortunately you were misinformed.
My MX record needs the extra subname (such as "mail") in front of the domain name, right?
Not at all. A MX record for 'N.com' is entirely valid (expected, in fact).
An MX record tells remote mail servers where to send mail for any domain/subdomain. If you think about it, let's say you worked for Apple and you wanted people to be able to send email to [email protected], well then you need an MX record for 'apple.com'.
You can see if you dig MX apple.com that they actually have 9 MX records, but the point still stands.
Now, you might also have MX records for subdomains so that you can have [email protected], [email protected], [email protected], etc. Each of these subdomains would need a separate MX record.
So, in general, for any set of email addresses @[anything.]domain.com you have a MX record telling remote mail servers where to send that mail.
Of course the MX record name is mail.N.com, but I think you are implying that the in the Mail settings of Server Admin where it asks for domain name all I need to put there is the N.com, right?
What I mean is that you need to set the domain name to whatever domain name you expect to receive mail at.
If you want users to have email addresses in the form of [email protected], then you enter 'N.com'.
If you want users to have email addresses in the form of [email protected] then you enter 'mail.N.com'.
If you want both forms, enter one in the main domain and add the other(s) in the Advanced -> Hosting -> Local Host Aliases section.
Is there anything in the Mail settings that needs to have the full MX record name (mail.N.com)?
Yes. Either the 'domain name' or the 'Local Host Aliases' needs to contain the same thing as your MX record. That's because the MX record tells remote servers to send mail to this machine, but the machine won't accept the mail unless it is configured to do so.
What is the "host name" supposed to be?
This should be the name that remote servers see when this machine tries to send outgoing mail.
Ideally this should match the reverse DNS of your IP address, that way when it connects to a remote server it says "Hi, I'm $hostname" and the remote server can lookup the machine's IP address and see the same result. This will reduce the problem of remote servers thinking you're sending them spam.
If you only have a single IP address then this probably needs to be something like 'N.com'. If you don't have control over your reverse DNS then you're going to run into a problem.
Also in the user accounts (in Workgroup Manager) what should the "mail server name" be? Is it the host name or the domain name?
Off hand, I don't know.
Also, why are all the default user email addresses [email protected] (the name I gave the server at setup)? Why doesn't the user accounts create [email protected] as the default address?
Presumably because the mail server says it is 'server.N.com' and therefore any accounts on that machine would be [email protected]. Changing the domain name (as above) should fix that.

Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid.

I'm stuck here trying to figure this error out.
2003 domain, 2012 hyper v core 3 nodes. (I have two of these hyper V groups, hvclust2012 is the problem group, hvclust2008 is okay)
In Failover Cluster Manager I see these errors, "Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid."
I restarted the host node that was listed in having the error then another node starts showing the errors.
I tried to follow this site: http://blog.subvertallmedia.com/2012/12/06/repairing-a-failover-cluster-in-windows-server-2012-live-migration-fails-dns-cluster-name-errors/
Then this error shows up when doing the repair: there was an error repairing the active directory object for 'Cluster Name'
I looked at our domain controller and noticed I don't have access to local users and groups. I can access our other hvclust2008 (both clusters are same version 2012).
<image here>
I came upon this thread: http://social.technet.microsoft.com/Forums/en-US/85fc2ad5-b0c0-41f0-900e-df1db8625445/windows-2012-cluster-resource-name-fails-dns-registration-evt-1196?forum=winserverClustering
Now, I'm stuck on adding a managed service account (mas). I'm not sure if I'm way off track to fix this. Any advice? Thanks in advance!
<image here>

Thanks Elton,
I restarted 3 hosts after applying the hotfix. Then I did the steps below and got stuck on step 5. That is when I get the error (image above). There
was an error repairing the active directory object for 'Cluster Name'. For more data, see 'Information Details'.
To reset the password on the affected name resource, perform the following steps:
From Failover Cluster Manager, locate the name resource.
Right-click on the resource, and click Properties.
On the Policies tab, select If resource fails, do not restart, and then click OK.
Right-click on the resource, click More Actions, and then click Simulate Failure.
When the name resource shows "Failed," right-click on the resource, click More Actions, and then click Repair.
After the name resource is online, right-click on the resource, and then click Properties.
On the Policies tab, select If resource fails, attempt restart on current node, and then click OK.
Thanks

ARD 3.5.1 DNS NAMES

Similar Messages

Maybe you are looking for