DNS - can't remove "0.0.10.in-addr.arpa" reverse domain!

Question

Level 2

221 points

DNS - can't remove "0.0.10.in-addr.arpa" reverse domain!

I'm having some trouble with DNS behind our firewall. In this case we have an internal block of IP's. We're using the public 10.0.1.xxx subnet. Using OS X Server's DNS service to attempt to add a virtual host to our to our previously working network has created some trouble. First of it always adds the Reverse Zone 0.0.10.in-addr.arpa. to our Zones list. The working one is 1.0.10.in-addr.arpa. so why does it insist on adding this other one? I delete it and save. But it reappears immediately...

It even shows in the log:
+03-Sep-2009 08:50:12.083 zone 0.0.10.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public: loading from master file db.0.0.10.in-addr.arpa. failed: file not found+

Server is running Leopard (10.5.8)

MB Pro, PowerMac, mini, iPhone, TV, Mac OS X (10.6)

Posted on Sep 3, 2009 11:32 AM

Reply

Answer 1

Sep 3, 2009 1:40 PM in response to Demetrios

I believe it is simply a server admin bug and doesn't effect anything in your DNS responses..

Test it..

From terminal,

% host 10.0.0.1

You can than try .2, .3, etc if you are interested...

Make sure your resolv.conf is pointing to your local dns server, if not,

% host 10.0.0.1 local-dns-server-hostname-or-ip

Reply

Answer 2

Demetrios Author

Level 2

221 points

Sep 3, 2009 5:12 PM in response to ColoradoMan

But I don't want that 10.0.0.xxx subnet to be managed.... unless for some reason OS X Server requires it?!?

I removed every trace of it from /etc/dns/publicView.conf.apple as per another thread's recommendation but now my single sign-on has gone all to ****...

is this 10.0.0.xxx necessary? if so, why?

Reply

Answer 3

Sep 3, 2009 9:39 PM in response to Demetrios

Hi,
When you set up your Kerberos realm on the original 10.0.x.x DNS zone with its accompanying x.0.10.in-addr.arpa then you established a required service. If you still had OD master with Kerberos running when you deleted the 10.0.x.x zone then Kerberos failed and kept trying to use the reverse pointer x.0.10.in-addr.arpa.

You will probably have to take the OD back to standalone after setting up the new zone with the new address and its reverse pointer. Give the new zone a different host name which results in a new realm. Then repromote OD and have Kerberos established with the new realm and DNS setup.

At this point it seems Kerberos is borked and you don't have much choice about going to standalone and repromoting to get it back.

HTH,
Harry

Reply