|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
I have all but given up getting DNS to work right on a server that is running two IP address, one on an internal DNS zone and one on an external DNS zone. I know there are issues with doing this if you do not have both DNS zones configured properly but I am pretty certain that the internal DNS server is configured correctly since none of my clients are having any issues at all. The only computer on the network that is having any issues is the server that is sitting on both zones. The server is running NAT and Firewall services and is also providing OD authentication services to the internal zone. The computer is set up with the internal hostname of fileserver.occu-med.com which is located at 10.0.0.1. The secondary interface (en1) is set up on the inside of the network, and the primary interface (en0) is set up on the outside of the network. If I run "host 10.0.0.1" in the terminal, I get "18.104.22.168.in-addr.arpa domain name pointer fileserver.occu-med.com." which is correct. If I run "host fileserver.occu-med.com" in the terminal, I get "fileserver.occu-med.com has address 10.0.0.1" which is also correct. Am I correct in assuming that forward and reverse DNS are set up correctly? If so, when I run "-sudo changeip -checkhostname" it returns: Primary Address = 209.234.xxx.x (External IP) Current Hostname = fileserver.occu-med.com DNS Hostname = mail.occu-med.net Technically, the Primary Address is correct (Have to have external interface set up as Primary in order for NAT to work properly) however I have no idea where the computer is pulling mail.occu-med.net as assigned to the external interface. The domain mail.occu-med.net is definitely NOT assigned to 209.234.xxx.x (that domain is hosted externally, and is assigned to our ISP's mail servers) and there is no internal occu-med.net domain. I did have this server set up as the DNS server when I was first messing around with it, so is it possible that the old DNS records are fudging things up? I recently switched all DNS services from this server to a Leopard server in the hopes that it would correct the issue. Unfortunately this didn't work. Does anybody have any pointers as to what the problem could be? Thanks, James _______________________________________________ Do not post admin requests to the list. They will be ignored. Macos-x-server mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.