[sciron]

More…. sorry.

Per https://www.afp548.com/article.php?story=20060503145111816#comments

don’t change that file I mentioned up there, change /etc/hosts instead, to reflect the proper hostname.

[sciron]

Bear with my questions as I am a Unix person thrown into an Apple world.

> The automounter would be looking for:
> /Network/Servers/servername.Psychology.McMaster.CA/Users/username

> While if you looked in /Network/Servers/ you will see:
> /Network/Servers/servername.psychology.mcmaster.ca

assuming that the next item after ‘Servers/’ is the FQDN, there is no issue there. However, why would you specify ‘/Network/Servers/servername.Psychology.McMaster.CA/USERS/username’ to mount? ‘/Users/username’ is NOT part of the FQDN. When specifying mount locations from another machine in Unice-land, you specify it thusly:

FQDN:/Users/username (or servername.psychology.mcmaster.ca:/users/username). The colon is the separator telling the system that that part is not part OF the FQDN name, but an object ON the FQDN object.
I know OSX handles things similarly because 1) it’s FreeBSD based, and 2) check out how to mount NFS, and specifics in FSTAB.

[sciron]

Potentionally some issues.
For starters, ‘named-checkzone’ and ‘named-checkconf’ can be handy tools, but do NOT rely on them religiously. And yes, they are included with OSX.
The .conf portion has an issue. It reads:
zone “128-26.55.158.72.in-addr.arpa” IN {
type master;
file “db.72.158.55.dev”;
};

It should read:

zone “55.158.72.in-addr.arpa” {
type master;
file “db.55.158.72.dev”;
};

The reasons being are:
1) IN can be omitted MOST places with Bind, you are not doing Chaosnet resolution are you?
2) the stuff between quotes after ‘zone’ MUST BE A PROPER reverse lookup zone. I must assume from your example that 72.158.55.0/24 is your network segment. This gets complicated in a minute if this is a public server and a public zone.
if your network segment for the zone is 192.168.1.0/24, you MUST SPECIFY the reverse zone in proper notation: 1.168.192.in-addr.arpa. It looks like you mixed some definitions up back up there.

Bind does NOT like empty lines in zone files. This may be platform specific, but it has been my exeperience with Bind in the x86 world that it pukes (not to mention its mentioned in the Bind documentation). Use ; for comments on those blank lines.
Next, your SOA definition is stated incorrectly. You have:
128-26.55.158.72.in-addr.arpa. IN SOA xserveoda.55.158.72.in-addr.arpa. support.aimaudit.com. (
2006052504 ; serial
2H ; refresh
2H ; retry
1W ; expiry
1D ) ; minimum

Which should be
@ IN SOA xserveoda.aimaudit.com. support.aimaudit.com. ( bleh )

The @ just simplifies things, Bind replaces @ with the zone name. You MUST SPECIFY your domain name server IN FORWARD NOTATION, not reverse.

; nameservers

128-26.55.158.72.in-addr.arpa. IN NS ns2.cl.bellsouth.net.
128-26.55.158.72.in-addr.arpa. IN NS ns3.cl.bellsouth.net.
128-26.55.158.72.in-addr.arpa. IN NS xserveobd.aimaudit.com.
128-26.55.158.72.in-addr.arpa. IN NS xservetwo.aimaudit.com.
128-26.55.158.72.in-addr.arpa. IN NS xserveone.aimaudit.biz.

****USE FORWARDERS for the above, it simplifies things unless you are doing zone transfers. It also allows for more customization later.

;hosts

130 IN PTR ImageONE-RAID.dev.aimaudit.com.
131 IN PTR aimwebserver.dev.aimaudit.com.
132 IN PTR 4dserverxp.dev.aimaudit.com.
133 IN PTR aimdlink1.dev.aimaudit.com.
134 IN PTR xraidc1.dev.aimaudit.com.

Hope it helps, bind can be a pita.

[sciron]

Why can’t I get these all in one response?

Sorry, but here’s what I just noticed:

May 9 18:30:08 ffserver1 servermgrd: servermgr_dns: configured name and reverse DNS name do not match (ffserver1.familyfuller.com != services.familyfuller.com), various services may not function properly – use changeip to repair and/or correct DNS
May 9 18:30:11 ffserver1 servermgrd: servermgr_dns: configured name and reverse DNS name do not match (ffserver1.familyfuller.com != services.familyfuller.com), various services may not function properly – use changeip to repair and/or correct DNS

Which means that, for some reason, your machine (ffserver1) is gettings the name ‘services’ on the ‘familyfuller.com’ domain. This isn’t a case sensitivity issue, it is an issue of an improperly configured DNS server.
If you are doing DHCP and DNS, scrap DHCP in favor of static addressing, until AFTER you get DNS working properly (dynamic updates to Bind are no easy task for the average techie in the beginning, but they are quite easy after you understand the pitfalls).
KISS=Keep It Simple Silly. Don’t load up your configuration with all of the settings until you have verified the operation of a few.

[sciron]

Sounds like a great reason to edit /etc/hostconfig.

[sciron]

One more thing, to find documentation for Bind and its zone files and configuration information, check with http://www.isc.org , the authors.

[sciron]

It literraly can not be a Bind (the DNS server in OS/X) or an OS/X issue [i] provided [i] apple did not bork the C library which performs such lookups.
By RFC definition, lookups and processing are case [i]insensitive[i].
Either Apple screwed the pooch on this one, or [more than likely] something else is generating this error.
SRV Records fall under the umbrella of requiring case independance.

[sciron]

Can you post your zone file and your zone definition in named.conf?

[Author]

Posts