Casper Server loosing DNS connection after a while!!!

mDNSResponder is Bonjour. Does your Xserve have FQDN? Have you confirmed configuration is correct? What does changeip come back with?

# sudo changeip -checkhostname

Don

Baykara, Cem Cem.Baykara at BSKYB.COM wrote"

I have repeated message in the system.log like below. It appears couple of hours after reboot my Casper Server and it stops server to communicate with domain controller!! This results I can not login to JSS using my AD credentials..

mDNSResponder[35]: AppendDNSNameString: Illegal empty label in name ".bskyb.com."

Any ideas, has anyone had this behaviour before? I don’t want to reinstall the OS X server 10.6.5, if I can fix it. Hardware is xServe Intel…JSS 7.31

Cem

I have bypassed load balancer and assigned fqdn to local ethernet port IP
instead of load balancer IP. What I have also noticed too was, if I change
PCI Ethernet Card as priority No1 it breaks AD login (LDAP LookUp) too.

sudo changeip -checkhostname

Comes up OK but still within an hour or 2, server loses dns connection

sudo changeip -checkhostname

Primary address = 10.0.0.1

Current HostName = myjss.mycomp.com

The DNS hostname is not available, please repair DNS and re-run this tool.

dirserv:success = "success"

------------------------------------------------------------

flush my DNS cache with dscacheutil -flushcache

Still not good.

However migrated the JSS to different Xserve (nice to have spare one :)
and all working perfect. My import plist/manifest issue also solved too =)

Anyway I am moving away from Xserve to Linux RedHat or WinServer Virtual
Server. I will be deploying JSS v8 to one of these options. Which one I
should go for? Any recommendation welcome.

Thanks!
Cem

I was having this issue with our server. Turns out, AD and DNS would both flake out. I've been running the following in a script daily and I haven't seen this happen since March.

#!/bin/sh

/usr/bin/net -n SERVERNAME -W DOMAIN.SAMPLE.COM -P ads dns register

For what it is worth we run two sets of DNS here. One is legacy, and
when we migrated over to an .org domain we got rid of that legacy DNS
but some systems still used it so when we deployed our Macs the network
admin input all the FQDNs of the servers with both domain entries. This
caused some OS X Servers to get a wrong DNS entry so I had them edit the
DNS database and use only the .org naming convention. Long story
short, no matter how many times I cleared DNS cache and used changeip to
fix the DNS it almost always came back. I think OS X Server caches
these settings deep somewhere and I just ended up wiping and reloading
the server.

I know this doesn't help you directly per se, but if your set up allows
for servers to be wiped and reloaded it only takes like an hour to do
so.