Hello,
we have a small SOHO network with a OSX Leopard Server. Active services are AFP, DNS, OD, Web, iCal. DHCP and some NAT is done by a router. The LAN IPs are in the 192.168.1.*** range. We have a dynamic IP, so to access Web services on the Server we use a dyndns address (myserver.dyndns.tv maps to the internal Web / WebDAV service).
This has been working without a hitch. Recently I had to change my ISP. Before we were on DSL, now it is cable. The new ISP does not seem to allow a loopback to self. Earlier, when I used “myserver.dyndns.tv” from inside my LAN, it would take me straight to the web server, as would 192.168.1.50 (server’s internal address). Now the external / dyndns IP cannot be reached from the inside – no result when accessing “myserver.dyndns.tv”, while “192.168.1.50” – or “myserver.elan” with elan being the internal zone name – works fine.
I figure I need to add a new entry in the DNS service. When I tried to add an entry to my zone (“elan”) that connects
myserver.dyndns.tv –> 192.168.1.50
I get no result. The log shows this:
22-Sep-2009 13:42:47.109 /var/named/zones/db.local.zone.apple:13: ignoring out-of-zone data (myserver.dyndns.tv)
22-Sep-2009 13:51:37.328 /var/named/zones/db.elan.zone.apple:17: ignoring out-of-zone data (myserver.dyndns.tv)
22-Sep-2009 13:51:37.334 /var/named/zones/db.elan.zone.apple:17: ignoring out-of-zone data (myserver.dyndns.tv)
What am I missing here? Surely it should be possible to configure DNS so that queries from within the lan for the IP “myserver.dyndns.tv” are rerouted to an internal IP (eg. 192.168.1.50)?
This is important since we need to sync iCal content from inside and outside.
Comments are closed