On Wed, Aug 15, 2012 at 2:39 PM, Ben Howell <[email protected]> wrote:
> I'm experimenting with a cluster in a new cell as part of a company-wide > upgrade of our current AFS infrastructure. However, our DNS no longer > supports custom non-TXT entries like AFSDB. Is there an alternative to > AFSDB? I have SRV records in place, _afs3-vlserver and _afs3-prserver. Is > there an SRV record for DB servers as well? Changing nameservers is not an > option, unfortunately. > Those *are* the DB servers (minus kaserver, but if you're using aklog you don't care and if you *are* still running kaserver for some reason then you should find a way to get rid of it ASAP). AFSDB was deprecated by the OpenAFS community when those SRV records became standard; if anything, you should be replacing it with the SRV records. I would suggest using strace (or similar OS-specific utility such as dtruss on OS X and Solaris or ktrace on *BSD) to find out exactly where aklog is hanging up. If it's hanging up looking for a nonexistent AFSDB RR, then it's actually a problem with your DNS server not returning the appropriate response to a failed query, and the workaround if you cannot get the DNS servers to actually speak the DNS protocol properly might be to rebuild OpenAFS without AFSDB support, or possibly run local caching nameservers. (Although I would think it'd check for the correct SRV RRs first and AFSDB only as a fallback.) Also, make sure the SRV records are what they're supposed to be. _afs3-prserver._udp.$cellname for whatever the cellname is. (Note, not the domain, not the Kerberos realm, *certainly* not a hostname.) -- brandon s allbery [email protected] wandering unix systems administrator (available) (412) 475-9364 vm/sms
