Resolving server DNS ?

I've been running Mavericks Server for a while, and use it for File Sharing, TM serving, and Cache serving. I'm about to upgrade to Yosemite and buy the server app
I keep seeing instructions that talk about "setting your router to resolve your server's name" and about configuring DNS.
e.g.
http://www.macworld.co.uk/review/utilities/os-x-server-review-3588390/
"For a basic server setup you might need to configure your router to resolve your server’s hostname, however, or simply edit your server’s hosts file to this end. OS X Server includes a DNS server you could also use."
I haven't done this. I can't see how to do this on my router. (BT home Hub 3). What are the advantages/purpose of doing this, and how do I do it? I do have a domain name, but it's hosted somewhere else. Everything seems to work ok.
Thanks

benwiggy wrote:
Hmm.
First, I have a dynamic IP address. It changes about once a month, or when I turn the router off and on. Does that mean I'll have to change the IP address in the DNS entry every time?
I presume I just create a new record on each device's hosts file?
Dynamic addresses complicate the issue. However, you can look at Dynamic DNS services. These are services that allow you to assign host names to dynamic services. An agent will run on your LAN and update the external DNS whenever it changes. It is nearly transparent to all users. Search for Dynamic DNS for more details.
I'm afraid the rest is just confusion. I understand that the point is so you can use the same hostname inside and outside the LAN -- but if my MBP has a DNS entry pointing to my public IP, then how does it switch inside the LAN? And how does it access my own website from inside the LAN if that domain name is pointing to the local server, not the webhosting one?
This is where DHCP plays its roll. You should not be hard coding network stack values in client devices. A DHCP server will hand out to the device the relevant stack info, including DNS server addresses. When you are on a LAN, the LAN's DHCP server will give you DNS server addresses. They may be servers on the LAN. Now when you ask for something from your domain, a LAN DNS server replies and routes you as appropriate. When the device leaves and joins a new network, a new DHCP server hands it new DNS server addresses. Now you hit those DNS server to route to resources.
From inside, you point to the external address of your web and mail server. That is how devices on the inside route externally for resources.
When you say "replicate the DNS on your LAN", do you mean turn on the OS X DNS server, and add a hostname with the local IP address? Or the public IP as well? So the local DNS server "over-rides" the DNS settings in the MBP's hosts file?
Sorry. "Not Normally This Stupid". I greatly appreciate your help in this.
Yes. Simple example.
Your LAN: 10.10.10.0/24
Your public IP: 17.13.11.7 (not accounting for dynamic)
Your Yosemite Server (cal.benwiggy.com): 10.10.10.5
Your Mail Server (mail.benwiggy.com): 17.34.68.10
Your Web Server (www.benwiggy.com): 17.34.68.11
Your Internal DNS would look like this:
A record for cal.benwiggy.com = 10.10.10.5
A record for mail.benwiggy.com = 17.34.68.10
A record for www.benwiggy.com = 17.34.68.11
(Your DHCP server on the LAN would hand out the address of your server as the DNS address, allowing all requests to hit it first)
Your external DNS would look like this:
A record for cal.benwiggy.com = 17.13.11.7
A record for mail.benwiggy.com = 17.34.68.10
A record for www.benwiggy.com = 17.34.68.11
Now, regardless of where devices are, they will find a destination.

Similar Messages

Unable to resolve server's DNS address.

Been sharing my internet (ethnernet) with another Mac OS X 10.6 via airport, but the other mac is unable to resolve server's DNS address. Help?

Hi,
Have you contacted your internet service provider (ISP) as DNS usually are ISP related. Have they reset their modem or router, not just power cycle?
I suggest you change the Preferred DNS server, try the following steps:
1. Click "Start", input "NCPA.CPL" (without quotation marks) and press Enter.
2. Right click on the connection that you use for the local connection, and then click "Properties".
3. Click to select "Internet Protocol Version 4 (TCP/IPv4)", and then click "Properties".
4. In the Internet Protocol window, let's change the "Preferred DNS server" to 208.67.222.222
5. Click 'OK' twice to complete the modification.
If the issue persists, please repeat the steps and change the "Preferred DNS server" to 208.67.220.220.
Also, if the issue persists, I suggest you run the following command:
ipconfig /release
ipconfig /renew
To get IP address & DNS from DHCP, the DNS server should be internal DNS server IP.
Hope this helps,
Ada Liu

An attempt to resolve the DNS name of a domain controller in the domain being joined has failed.

"An attempt to resolve the DNS name of a domain controller in the domain being joined has failed."
This is the error message I get whenever I try to connect to my servers domain which I just set up earlier today. I have read through a bunch of other threads on the same error message
but each of them has had different solutions and none of them have helped me.
The one thing that I suspect is related to my problem is that I can't ping my domain on the W7 computer I'm trying to connect. I can ping the server, but not the domain. the domain
i'm using is set up like "domain.local" .
Other things that might be relevant.
I'v already set up user accounts and a computer under the Server 2012 active domain administrator settings.
I'v port forwarded ports 80 and 443 on the server.
The server has a static IPv4 IP adress. I haven't done anything with IPv6
The W7 computer has a dynamic IP adress, but I don't think it changes. I believe my router is set up to keep it constant, not 100% sure though.
Thanks for any help with this, I'm pretty much out of ideas on this.

Hi ZachPrinz,
Firstly, would you please let us know the outputs of ipconfig /all both of the clients and the DC.
Also, if you run nslookup FQDN of your DC from your clients, what will you receive?
Meanwhile, regarding the issue, we can refer to
the similar thread and see how it works.
More information:
Troubleshooting Domain Join Error Messages (en-US)
Hope this helps.
Jeremy Wu
TechNet Community Support

Lion Server DNS service not working for locally created zones. Caching working fine.

OS Lion Server DNS service not working for local zones. Was fine under Snow leopard server but Lion server upgrade has severely broken my DNS and web sites. Zones look fine under Server Admin but keep getting "query failed (SERVFAIL) for xxxx at /SourceCache/bind9/bind9-42/bind9/bin/named/query.c:3921" in the logs. BTW - Server Admin cant seem to see the log file either.
Surely someone actually tested that DNS still worked on Lion?

I upgraded from Snow Leopard Server to Lion Server on day 01. I hit the same issue where, after the upgrade, my Lion Server stopped serving names for my private local domain.
I finally took a few minutes to figure out what was wrong. After turning on debug logging and looking through the logs, I found my particular issue, now resolved.
The issue I had was, when the domain initially was setup when I installed Snow Leopard Server, for some reason it created a zone just for the server (in my case, something like zone "s-01.mydomain.priv"), and a separate zone for all the other machines (zone "mydomain.priv", containing all the private IPs for my local domain). I never messed with it because it worked, but generally I would have put all of them in the same zone.
My zone "mydomain.priv" had a nameserver and mail exchanger entry for my server, s-01.mydomain.priv. I could see this in the Server Admin app on the DNS bubble, Zones tab, mydomain.priv selected, and the General Info panel. This was fine in Snow Leopard. This was failing the zone load in the updated bind for Lion Server, though. The issue was that the "mydomain.priv" zone was referencing the s-01.mydomain.priv server, which was not defined in the "mydomain.priv" zone but rather in the "s-01.mydomain.priv" zone.
My fix:
1. In Server Admin, add the server to the zone "mydomain.priv". I put an A record (Add Machine) in the "mydomain.priv" zone for my server named s-01.mydomain.priv.
2. shut down DNS on the OS X Lion Server (hit the Stop DNS button on Server Admin).
3. edit /etc/named.conf by hand, removing the specialized zones that contianed just the server. In this case, it would be the section titled 'zone "s-01.mydomain.priv"' and the section titled 'zone "3.10.1.10.in-addr.arpa"'. Your in-addr.arpa zone name will change based on whatever your server IP address was. My internal one happened to have s-01.mydomain.priv mapped to 10.1.10.3.
4. Once the specialized zones for just the server were removed, I started the DNS up again. Instead of serving four zones as it had in OS X Snow Leopard Server, it now servers two zones. And, now, it is resolving my local machines for the mydomain.priv zone.
YMMV. I did note that it wasn't totally necessary to do step 3, but I never really understood the need for the specialized domain, and keeping it around would have a copy of data that would just confuse things.
Hope that helps. That's been the only hiccup I've noticed updating to OS X Lion Server thus far.

OS X Server DNS Best practice?

Hello,
I am having a little trouble with my OS X Server DNS.
I have set up server.example.com and that works fine but now from my internal network I cannot get to:
example.com or
www.example.com
example.com is a website I have set up on a remote webserver.
My records currently look like this.
Primary Zone: example.com
server.example.com - machine
server.example.com - nameserver
Reverse Zone: 50.168.192.in-addr.arpa
192.168.50.25 - reverse mapping
server.portalpie.com - nameserver
My webserver for example.com has an IP of something like 175.117.174.19
How would I get example.com and www.example.com to point to 175.117.174.19?
Thanks

tsumugari wrote:
Hello, DNS for simple name resolution work correctly for internal and external name. Internal it is .lan and external .fr
I think there is perhaps SRV entry to add.
Please do not use .LAN as your top-level domain. That's not a valid top-level domain right now, but it's also not reserved for this sort of use. Either use a real and registered domain, or a subdomain of a real and registered domain, or — if you squat in a domain or try to use a TLD that's not registered — expect to have problems as new top-level domains are added. At the rate that the new TLDs are coming online from ICANN, I'd expect to see .LAN get allocated and used, too.    .GURU, .RIP, .PLUMBING and dozens of other new top-level domains are already online, and probably thousands more are coming online.
SRV records are not related to accessing the Internet, those are service records which some applications use to access certain network services; they're a way to locate a target server and a port for specific applications — CalDAV does use an SRV record, but that's not related to the original posting's issues.   If you're having issues similar to the OP, then access your server and launch Terminal.app from Applications > Utilities and verify local DNS with the (harmless, diagnostic) command-line command:
sudo changeip -checkhostname
Enter your administrative password. That command might show a one-time informational message about the use of sudo, and will usually then show some network configuration information about your server, and then an indication that no problems were found, or some indications of issues. If there are errors reported, your IP network or your local DNS is not configured correctly — I'm here assuming a NAT network.
I usually do this DNS set-up in a couple of steps. First, get private DNS services configured and working. This is always the first step, right after assigning the IP addresses.   It's just too convenient not to have DNS running on your local LAN, once you get to the point of having and running a server.   Then for external access for (for instance) web services, get port-forwarding working at the firewall/NAT/gateway box working; get your public static IP address mapped to the server's internal, private, static IP address. Then get the public DNS configuration to resolve your external domain name to your public static IP address.
My preference is to use separate DNS domains or a domain and a subdomain inside and outside. Using real and registered domains, and not using any domains associated with a dynamic DNS provider — that's possible, but a little more tricky to configure. This internal and external domain usage simplifies certain steps, and it avoids having to deal with cases where — for instance — some of your services have public IP addresses — such as a mail server you might be using — and other services might be entirely private. If you have one domain (or subdomain) be public and one be private, then you don't have to track external IP address changes in your private DNS services; public DNS has just your public stuff, and your private domain (or subdomain) has just your private stuff. Also obviously easy to tell what's inside your firewall, and what's outside, using this.
If you're thinking of running a publicly-accessible mail server, you'll need additional steps in the public DNS.
Little of the above probably makes sense, so here's a write-up on configuring DNS on OS X Server.   All of the Server.app stuff works about the same for general DNS setup, too. More recent Server.app is usually more flexible and capable than the older Server.app stuff, though.

Unable to resolve external DNS

Hi All,
I have recently set up an Xserve running OS X Server 10.3.4 with Network Home Directories. Everything works well and clients are able to log in and see their home directories. However, we use a web proxy server which relies on there being certain DNS in the clients Network Preference Pane so we can surf the web. In order for the home directories to work I have to have the IP of the server in the DNS of the client which results in the clients not being able to surf.
I believe the best way to achieve this is to get the Xserve to resolve external DNS but I can't figure out how to do this. Everywhere I search, the results seem to be for Tiger server!
It took me a while to get the home directories sorted and now I'm stumped - its driving me mad!
Any help would be much appreciated!
Thanks
PowerBook G4 15" 1.5Ghz Mac OS X (10.4.3)

Those solutions will acheive the same effect. I like mine, simply because it doesn't require you to differentiate forwarding based on whether the lookup is a local or non-local zone (i.e. it's simpler).
To make a backup of your BIND config file, do something like:
'sudo cp /etc/named.conf /etc/named.conf.backup'
also a good idea to backup the contents of the '/var/named' folder once in a while, as Server Admin has been known to break it's own zone files from time to time.
Many thanks for your reply. I have been looking at a
similar solution after trawling the discussions site
but it conflicts with your answer:
http://discussions.apple.com/thread.jspa?threadID=1317
98&tstart=75
Also, how would I go about backing up tge named/conf
file?
iBook G4 Mac OS X (10.4.3)

Tiger Server DNS and OpenDNS

Setup:
Tiger Server 10.4.9, OD Master, DNS on
I would like to use OpenDNS as my forwarders but I'm not sure of the proper syntax when editing the etc/named.conf file.
The OpenDNS IPs are:
208.67.222.222
208.67.220.220
Currently, my client machines have the IP of my Tiger Server as their DNS server. I'm hoping that by adding forwarding to the named.conf file, my client machines would be able to resolve internal DNS AND take advantage of OpenDNS for everything else.
I also imagine I would have to turn Zone Transfer and Recursion OFF in Server Admin?
Many thanks.

I found it by doing a more thourough search. For anyone interested here it is:
forwarders {
208.67.222.222;
208.67.220.220;
forward first;
This should come right after this line in your /etc/named.conf file:
// query-source address * port 53;
In Server Admin, in the DNS section:
Zone transfer should be OFF
Recursion should be ON
On your client computers, all you need to put in (in the DNS section of the Network preferences) is the IP of your Tiger Server machine.
Hope that helps anyone else.

Microsoft Windows Server DNS Monitoring v7.1.10100.0 High CPU Usage on Windows Server 2012 R2

Hello!
I've a big problem with this MP. When the zone monitoring is enabled (by default) the MonitoringHost.exe takes up all the CPU. I've put the zones in Maintenance mode.
I've got this problem only with a new Windows 2012 R2 server. Other Windows Servers (2003 R2, 2008 & 2008 R2) with DNS Server Role they don't have this problem.
Any ideas?
Thank you!
The configuration is:
SCOM 2012 R2
Microsoft Windows Server DNS Monitoring v7.1.10100.0 Management Pack
DNS Management Pack Action Account has been configured
"Act as proxy..." is enabled
The monitored server config:
Windows Server 2012 R2 (standalone)
DNS Server Role installed
DNS Management Pack Action Account is a member of the "Administrators" group
The only events I've are the following but I'm not sure if they're related (because of the ...DNSSEC...):
Log Name:      Operations Manager
Source:        Health Service Modules
Date:          8/11/2013 11:16:21
Event ID:      11903
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      NS2...
Description:
The Microsoft Operations Manager Expression Filter Module could not convert the received value to the requested type.
Property Expression: Property[@Name='QueriesResponded']
Property Value: Property[@Name='QueriesResponded']
Conversion Type: DataItemElementTypeInteger(5)
Original Error: 0x80FF005A
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries
Instance name: <zone-name> on NS2...
Instance ID: {4BCB4738-1287-2E6F-E0AA-1FF8D66DDB0B}
Management group: <grp-name>
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Health Service Modules" />
    <EventID Qualifiers="49152">11903</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-08T09:16:21.000000000Z" />
    <EventRecordID>9602</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>NS2...</Computer>
    <Security />
</System>
<EventData>
    <Data><grp-name></Data>
    <Data>Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries</Data>
    <Data><zone name> on NS2...</Data>
    <Data>{4BCB4738-1287-2E6F-E0AA-1FF8D66DDB0B}</Data>
    <Data>Property[@Name='QueriesResponded']</Data>
    <Data>Property[@Name='QueriesResponded']</Data>
    <Data>DataItemElementTypeInteger(5)</Data>
    <Data>0x80FF005A</Data>
</EventData>
</Event>

Glad to see you found the solution and thanks for your sharing.
Niki Han
TechNet Community Support

Strange behaviour of OS X Server DNS with IPv6 reverse zones

I am running a full IPv4 / IPv6 dual stack setup across several machiens including a server (OS X 10.9.1 / OS X Server 3.0.2). I also have IPv6 Internet access via TunnelBroker and have a /64 prefix assigned to me. All my systems have valid and correct IPv6 addresses (not temporary ones) from the range denoted by that prefix.
I have setup IPv4 and IPv6 addresses for all my systems in OS X Server DNS and that works fine. However, when I add an IPv6 address for a system, the DNS server (or maybe the server GUI) insists on creating a reverse zone for the /127 version of the address. This means I pretty much have a separate reverse zone for every system, which seems crazy to me. it is especially annoying as I have another DNS server where all my zones are defined as slave zoes (for availability reasons) and thsi makes the process of addign a new IPv6 host somewhat tedious. I tried pre-creating a properly named reverse zone for the /64 prefix but the DNS server would not use that and still persists in creating these strange zones.
Here is a (fictitous example)...
My /64 prefix is 2001:fd0:f19:2ab::/64
I have a system with an address of 2001:fd0:f19:2ab:7e6d:62ff:fe8a:a84c
I add this to OS X Server DNS and it created the reverse DNS zone:
4.8.a.a.8.e.f.f.f.2.6.d.6.e.7.b.a.2.0.9.1.f.0.0.d.f.0.1.0.0.2.ip6.arpa
whereas I would expect it to instead add it to the zone
b.a.2.0.9.1.f.0.0.d.f.0.1.0.0.2.ip6.arpa
if that zone already exists.
Has anyone else noticed this? Or do you have it working as one might expect?

Chris..
I, too, have the same problem. I take issue with much of the OS X "Server" after it has been so completely dummed down that it is virtually useless for anyone that would actually like to utilize it as an actual, as the name implies, "SERVER." I won't get into all of the details of everything that drives me crazy with Apple's decisions here but, suffice it to say, I am EXTREMELY DISAPPOINTED with Apple more than ever. They should, at a minimum, offer a full-fledged server like they used to have, for an additional price, for people that need more than a nice looking interface and a worthless box.
That being said, the DNS server, like the rest of the OS X Mavericks Server, is dummed down to the point of allowing very little customization. Short of using the command line, which I have decided to do (I scrapped the OS X server all together, and just set up BIND, openLDAP, DHCP, Quagga, etc. from the CLI just like I do with all of my Linux servers), there is not much you can do to get the correct prefixes to show up in IPv6 reverse zones. The reason is that when you enter the forward record, the interface does not give an option to enter the prefix. So, it seems that for EACH AND EVERY v6 entry (AAAA record) you have (or at least every 10 entries), you will get a separate reverse zone.
To be completely honest, I don't even know why they included IPv6 zones in this implementation because it is totally out of compliance with the RFCs and, obviously, will not provide proper and correct reverse lookups. How could it? As you pointed out above, with a /64 prefix, you're getting a 31 digit long reverse zone (which, btw, is a /124)...***??? I've never heard of such a thing. There should be 16 digits in a /64, 12 in a /48, 8 in /32 and so on.
I don't think it is anything to do with your using a tunnel broker -- all of our systems are native IPv6 and all reverse queries to the Mac Server fail.
I can tell you how to use the CLI to manually enter the zones with the serveradmin tool, if you like, but my advice is to just move to a full fledged BIND implementation .... and, if you want some type of interface other than the console, use something like Webmin which has a GREAT DNS zone interface...and it also keeps up with the RFC compliance.
Just message me back if you'd like the shell commands. I hate to say this, it literally pains me, but I administer a ton of servers (physical and virtualized)... roughly 1000 +- to be exact...and WINDOWS Server has a DNS server that is so much further ahead and ADVANCED than Mac, it is disgusting. In fact, we are running 12 Win Server 2012R2 Active Directory Domain Servers, each running synchronized DNS records and even with over 250,000 DNS records, it works like a champ. Still, our primary and fail-safe DNS servers are all BIND v9. Like I said, it is awful to say that about Mac, but dude, they need to wake up and either get back to the real-deal systems or just get out of the advanced product arena all together. (one exception...my new MacPRO is AWESOME and the most advanced piece of computing equipment money can buy for the price...so kudos there)
Sorry about the rant, but when i read your post, I was reminded how frustrated I am at all of this nonsense.
Take care...and good luck.

Client wont resolve central server dns

hi,
when installing the client, it wont connect to the central server by dns name, only by ip.. even though the machine i'm installing on CAN resolve the name to the correct ip. this happens on any machine i install on.. does this client use its own dns or something ?
thanks.
This topic first appeared in the Spiceworks Community

Microsoft is ending Windows Server 2003 support on July 14, 2015, when the popular platform will no longer receive security updates. End of life migration is a serious transition for organizations, and many will keep the using outdated platforms long after the deadline. How should organizations that are still in transition prepare for the inevitable […]…Read MoreThe post Security Slice: Severing Windows Server 2003 appeared first on The State of Security.
Read More

New, Single Server - DNS, Web, Wiki, Mail Setup Issues

I'm having some issues properly setting up 10.7.3 to host internal DNS and external Web, Wiki and Mail. I'm having issues with the web and wiki hosting. Since those are the most important right now, I haven't really had a chance to fully test the other features. I was able to do some testing of the mail and iCal but it was limited.
Long read below but I thought the specifics would be helpful...
My goals and configuration are:
***GOALS***
Primary:
1) Host a public website: example.org and www.example.org
2) Host a public wiki: main.example.org and www.main.example.org
3) Host a public mail server: [email protected]
4) Host a public, group calendar
4a) Read only to majority - Read/Write to a group
5) Host a global address book for authenticated users
Secondary:
6) Allow anonymous public access to a file share (read only)
7) Allow authenticated access to the same file share (read/write)
8) Do as much of this via GUIs as possible.
***SETUP AND CONFIGURATION***
Physical:
1) Business class Internet (no blocked ports)
2) A single, public and static IP address
3) Domain name and public DNS via GoDaddy
4) Wildcard Cert: *.example.org from GoDaddy
5) Late 2011 (bought in Jan 2012) MacMini Lion Server (the $1,000 one).
5a) Upgraded the RAM to 16GB (need for VMware Windows clients)
5b) Added two USB to Ethernet adapters.
6) Using a new model AirPort Extreme Base Station (bought w/ the MM) as the main router.
Initial Configuration:
7) Setup a Mac Address reservation for the main and two USB Ethernet ports along with the wireless too.
7a) Main port = 10.0.1.5 / Others are .6, .7 and .10
8) During the setup, I chose the Host on the Internet (third) option and named my server: main.example.org
9) After the setup completed, I upgraded the OS & Admin Tool to 10.7.3 from a clean install (on #5 now)
DNS Config
10) I used the admin tool to open DNS and change:
11) "Primary Zone Name" from main.example.org to example.org.
12) In the "Nameservers:" block, I changed the zone name there but left the nameserver name alone (zone: example.org /// Nameserver Hostname: main.example.org).
13) The Machine Name and Reverse Zone was left alone. RZ resolves to main.example.org. sudo changeip -checkhostname is good. dig on the example.org and main.example.org are good to go (NOERROR).
OD Config
14) From the server app, I clicked Manage/Network Accounts and setup the OD - No issues.
SSL
15) From the server app, I created self signed cert, generated a CSR, got a public Cert, then replaced the self-signed with the public one - No issues.
16) Changed any service using the self-signed cert to the public one - No issues.
17) Changed the cert in the OD to the public cert from server admin - No issues.
In order: File Sharing, Mail, AB, iCal, Web, Wiki, Profile Manager, Network Groups, Network Users
18) File Sharing was setup using the server app
19) Setup mail using the server app to start it and the server admin app to configure it - No issues there (I think...)
20) AB - Flipped the switch to on
21) iCal - Flipped the switch to on - I setup the e-mail address to use after I added the network accounts.
22) Web - Flipped the switch to on - Default site worked (main.example.org)
23) Wiki - Flipped the switch to on - Default wiki worked. (main.example.org)
24) PM - Checked the sign config profiles and enabled the device mgt. I then flipped the switch to on - Default settings and pages worked.
***MY PROBLEMS***
Website:
Adding a website for example.org gave me the red dot in the server app. To fix that, I added a Machine Name record to my primary zone (PZ = example.org Machine Name = example.org). I first tried using the same 10.0.1.5 IP as the main.example.org and left the reverse mapping alone (still resolved to the NS of main.example.org).
That gave me the green light in the server app when trying to add the website again. From there, I changed the "Store Site Files In" to the location of my website files (and confirmed "Everyone" has Read Access in the folder's security settings). I left the other info alone (all defaults accepted) and clicked done.
Access to the website works on the server but external access doesn't (Network Error/timed out tcp_error). Checked the AirPort settings using the AirPort utility (version 5.5.3) and the Port Mapping (under the "Advanced" icon) show serveral services all pointing to 10.0.1.5. Thinking it could be DNS I tried main.example.org externally and it failed the same way.
I ran the changeip command (good to go) and dig on example.org and main.example.org and they both resolved to 10.0.1.5 correctly.
I removed the example.org Machine Record from the zone and it now looks like:
PZ=example.org / ZONE=example.org / NS=main.example.org
Machine Record=main.example.org / IP=10.0.1.5
RM=10.0.1.5 / Resolves=main.example.org
PLEASE HELP!

The amount of users (if relevant):
On site - 1 (Me)
Off site - 16 (Windows clients - some have iOS devices too)
Web site traffic - less than 50 regular visits per day (avg of 15) with a peek of ~125 once a month.
This is for a 501c3 public nonprofit made of all unpaid volunteers (including the officers and directors). All of us have paying day jobs and I just so happen to be the guy that knows just enough to get myself in trouble here.

Clients fail to resolve local DNS names, external names working fine

Hi there,
I've a strange issue with a couple of domain joined computers. Resolving internal and external host names works fine with nslookup. But clients loose AD connectivity because they can't resolve host names from the local DNS zones outside of nslookup.
Pinging IP addresses always works.
So far only notebook computers are affected. Desktop computers work fine. OS is Windows 7/8/8.1 for clients and Windows Server 2008 R2/2012 for AD DCs/DNS servers.
Example:
C:\>nslookup bl-sphv00
Server: bl-spdc01.bl.local
Address: 192.168.154.21
Name: bl-sphv00.bl.local
Address: 192.168.154.10
C:\>ping bl-sphv00
Ping request could not find host bl-sphv00. Please check the name and try again.
C:\>ping bl-sphv00.bl.local
Ping request could not find host bl-sphv00.bl.local. Please check the name and t
ry again.
C:\>ping 192.168.154.10
Pinging 192.168.154.10 with 32 bytes of data:
Reply from 192.168.154.10: bytes=32 time=52ms TTL=128
Reply from 192.168.154.10: bytes=32 time=51ms TTL=128
Reply from 192.168.154.10: bytes=32 time=52ms TTL=128
Any help appreciated.
Thanks a lot.
Te.Be.

Hi there,
a Microsoft support guy send me a solution earlier posted under
http://social.technet.microsoft.com/Forums/windowsserver/en-US/f49b8398-d923-4e7e-86e7-78094113c091/problems-with-dns-and-ad?forum=winservergen
To get the client work again you just have to delete a few registry keys set by DirectAccess GPOs using this little batch:
@echo off
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient\DnsPolicyConfig" /f
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator\CorporateConnectivity" /f
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\Tcpip" /f
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityAssistant\DTEs" /f
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityAssistant\Probes" /f
reg delete "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" /v SMB1NATCompatibilityLevel /f
Unfortunately this breaks the clients DirectAccess configuration and leaves me without a real solution. Found some hints here:
http://blogs.technet.com/b/tomshinder/archive/2010/03/13/uag-directaccess-group-policy-assignment-make-sure-the-right-policies-are-applied.aspx
So my question is now: How do i have to edit the wizard generated DirectAccess GPOs correctly?
Anyone any idea?

10.6.4 Server on Mini Server - DNS Problems - Slow, EDNS log messages

Like a few of other people here, I'm having a hard time getting DNS to work smoothly on my new Mac Mini Server, now running Snow Leopard Server 10.6.4. I'd been running Leopard Server on a previous machine with much smoother DNS (though the Server Admin config didn't work, that's another story).
Resolution takes a very, very long time and eventually I'll get messages in the log saying 'success resolving 'xxxxxx' after reducing the advertised EDNS UDP packet size to 512 octets'.
I've searched everywhere and there seem to be two reasons why this is happening:
1. The DNS server is stopping responding on TCP, and is only responding on UDP;
2. Some other portion of my network (maybe the router) doesn't like UDP packets bigger than 512 octets.
For the first - is there any way I can fix this within OS X Server? There is no problem in the network since the router itself (running Linux) can resolve via TCP (using the forwarder addresses that are set up in my OS X Server config) instantly, and any clients that I switch from using the internal OS X Server (for DNS resolution) to use an external resolver work immediately too. I'm not sure why the daemon on OS X Server stops listening on TCP port 53 and only accepts UDP - and then only forwards on queries via EDNS via UDP - which is where I seem to have a problem.
Secondly - can I disable EDNS somehow and just do plain old DNS?
Some of the threads point to routers that don't like UDP packets over 512 octets, some point to firewalls and adaptive code that closes off ports when an app tries too many times, etc. I've opened ALL firewalls - turned off the OS X Server firewall, turned off the SPI firewall in the router (it's a Netgear DG834 with the DGTeam custom firmware), and I'm as far as I can go without buying a new router.
If the only answer is 'OS X Server needs a better router' then I'd appreciate what router I should buy - this situation is becoming untenable since the DNS resolution performance of my entire network is unpredictable, and I don't want to have to reboot the Server on a regular basis when there are loads of clients and their home directories sitting on it, since OS X Client gets twitchy when your home folder vanishes off the network…
I'm happy hacking config files - but can't seem to see anything in the DNS config that would allow me to either turn off EDNS or restrict the packet size to 512 octets (there's a comment in the config file that the directive is ignored for this one, fat lot of help that is). As to why the server itself stops listening to TCP port 53…. I have no idea and I can't find a solution with a search.
So in the absence of solutions - can anyone help me with a workaround? The only 'answered' question in this domain was 'answered' with the OP finding a workaround in their router firmware that changed the DNS cache packet size. I can't find anything like this in my router config, so I can't use this workaround. Are there any workarounds I can apply to my OS X Server, that don't rely on my router?
Yes, I know the router isn't that special, but it's a small business network. Advice on an upgrade would be welcome but doesn't solve the problem for me now. I'm based in the UK, if anyone also in the UK can recommend a suitable small-business NAT router I can use then I'd find that helpful, but I don't want to be told to purchase an enterprise-class router, turn off NAT and be recommended a store in the USA as it won't be that helpful
Ideally there'd be a way to tweak the DNS server on OS X to not bother with EDNS, or to stick to 512 octet sized packets (can I do this globally for all UDP from my server?), or to keep working on TCP…
Anyone know? The machine hosts client homes internally and serves mail, web and DNS externally. It's not a high-traffic system and it sits at the end of a business-grade ADSL line. I'm not being DoS'd - this behaviour seems random as to when it strikes. I try to restart the named daemon on the server when it strikes, but I need to be on the network to make that happen….
Solutions appear to be out, but I'd really appreciate a workaround. Many thanks in advance!

Hi Rob,
Not much of a MAC person myself however this support matrix might help:
http://www.adobe.com/products/coldfusion/coldfusion7/pdfs/cfmx7_systemsupportmatrix.pdf
Seeing your getting a few Java errors perhaps the JVM in CF7 1.4.2_09 is too early for MAC OS 10.6.4?
HTH, Carl.

OSX Yosemite 10.10.2 Server - DNS Issue

I am trying to set up Yosemite server a home server for the family - 5 macs. I have a public domain name which is forwarded to a Draytek ADSL router. The Mac Mini running Yosemite (server) sits behind the Draytek on a private network (192.168.6.X). It was a clean install (not an upgrade), DNS works for most things (e.g. safari & Open Directory), but DNS appears to have issues resolving some domain names (particularly anti-virus updates) ... an excerpt from the log follows. it seems no fail to resolve TXT records properly and also partial records e.g../NS/IN.
Any help and/or pointers would be greatly appreciated.
Thank you
Simon
23-Mar-2015 13:53:17.818 error (host unreachable) resolving 'current.cvd.clamav.net/TXT/IN': 2a01:4f8:160:8421::2#53
23-Mar-2015 13:53:17.818 error (host unreachable) resolving 'current.cvd.clamav.net/TXT/IN': 2001:4b78:2000::1#53
23-Mar-2015 13:53:19.588 error (host unreachable) resolving 'ns.taint.org/AAAA/IN': 2001:500:1::803f:235#53
23-Mar-2015 13:53:19.588 error (host unreachable) resolving './NS/IN': 2001:500:1::803f:235#53
23-Mar-2015 13:53:19.589 error (host unreachable) resolving 'ns.taint.org/AAAA/IN': 2001:503:c27::2:30#53
23-Mar-2015 13:53:19.589 error (host unreachable) resolving './NS/IN': 2001:503:c27::2:30#53
23-Mar-2015 13:53:39.813 error (host unreachable) resolving './NS/IN': 2001:500:2d::d#53
23-Mar-2015 13:53:40.882 error (host unreachable) resolving 'local/SOA/IN': 2001:500:2d::d#53
23-Mar-2015 13:53:40.882 error (host unreachable) resolving 'local/SOA/IN': 2001:500:2f::f#53
23-Mar-2015 13:53:41.749 error (host unreachable) resolving 'local/SOA/IN': 2001:7fe::53#53
23-Mar-2015 13:53:41.749 error (host unreachable) resolving 'local/SOA/IN': 2001:500:3::42#53
23-Mar-2015 13:53:45.005 error (host unreachable) resolving './NS/IN': 2001:7fd::1#53
23-Mar-2015 13:53:45.226 error (host unreachable) resolving 'local/SOA/IN': 2001:7fd::1#53
23-Mar-2015 13:53:45.226 error (host unreachable) resolving 'local/SOA/IN': 2001:503:ba3e::2:30#53
23-Mar-2015 13:53:46.924 error (host unreachable) resolving 'local/SOA/IN': 2001:500:1::803f:235#53
23-Mar-2015 13:54:28.158 error (host unreachable) resolving 's.mzstatic.com/A/IN': 2001:503:a83e::2:30#53
23-Mar-2015 13:54:31.601 error (host unreachable) resolving 'a1.da1.akamai.net/A/IN': 2001:503:231d::2:30#53
23-Mar-2015 13:54:31.741 error (host unreachable) resolving 'su.itunes.apple.com.edgekey.net/A/IN': 2001:503:231d::2:30#53
23-Mar-2015 13:54:32.068 error (host unreachable) resolving 'a2.da1.akamai.net/A/IN': 2001:503:231d::2:30#53
23-Mar-2015 13:58:24.002 error (host unreachable) resolving './NS/IN': 2001:7fe::53#53
23-Mar-2015 13:58:24.002 error (host unreachable) resolving './NS/IN': 2001:7fd::1#53
23-Mar-2015 13:58:24.002 error (host unreachable) resolving './NS/IN': 2001:503:c27::2:30#53
23-Mar-2015 13:58:24.002 error (host unreachable) resolving './NS/IN': 2001:503:ba3e::2:30#53
23-Mar-2015 13:58:24.868 error (host unreachable) resolving './NS/IN': 2001:500:2d::d#53
23-Mar-2015 13:58:24.868 error (host unreachable) resolving './NS/IN': 2001:500:3::42#53
23-Mar-2015 13:58:24.868 error (host unreachable) resolving './NS/IN': 2001:500:1::803f:235#53
23-Mar-2015 13:58:26.581 error (host unreachable) resolving './NS/IN': 2001:dc3::35#53
23-Mar-2015 13:58:27.456 error (host unreachable) resolving './NS/IN': 2001:500:2f::f#53
23-Mar-2015 14:16:46.184 error (host unreachable) resolving './NS/IN': 2001:7fe::53#53
23-Mar-2015 14:16:46.184 error (host unreachable) resolving './NS/IN': 2001:7fd::1#53
23-Mar-2015 14:16:46.184 error (host unreachable) resolving './NS/IN': 2001:503:ba3e::2:30#53
23-Mar-2015 14:16:47.124 error (host unreachable) resolving './NS/IN': 2001:500:2d::d#53
23-Mar-2015 14:16:48.070 error (host unreachable) resolving './NS/IN': 2001:503:c27::2:30#53
23-Mar-2015 14:16:49.964 error (host unreachable) resolving './NS/IN': 2001:500:3::42#53
23-Mar-2015 14:16:49.964 error (host unreachable) resolving './NS/IN': 2001:500:1::803f:235#53
23-Mar-2015 14:16:49.964 error (host unreachable) resolving './NS/IN': 2001:dc3::35#53
23-Mar-2015 14:16:49.964 error (host unreachable) resolving './NS/IN': 2001:500:2f::f#53

As Linc says those examples are all IPv6 lookups.
Even if your Draytek supports IPv6 which I believe some current models do, it is highly possible your ISP does not support IPv6 as far as your connection is concerned. (As an aside since officially IPv4 addresses have run out worldwide, it is outrageous how most consumer ISPs still fail to offer proper IPv6 connections to customers.)
You might want to try experimenting with turning off IPv6 completely on your Mac server and/or clients. This is done in System Preferences -> Network. Or you can do this in Terminal.app as follows.
Turning off IPv6 support for ethernet:
networksetup -setv6off Ethernet
Disabling IPv6 for wireless:
networksetup -setv6off Wi-Fi

Unable to resolver server name

when I open a terminal window and type ping followed by existing server name it says "cannot resolve reference: unknown host"
if I do the same thing on a PC it all works!
Why can't a MAC find other computers connected on the same network
It such a basic thing, It almost make the imposable to us a mac. One way other people use to get around this problem is to run windows on a mac instead, But I don't understand why.

Check out this link - http://discussions.apple.com/thread.jspa?threadID=2496619&tstart=15
It might assist in isolating/troubleshooting the issue. Can you ping via Network Utility? Did you try and DNS cache flush?

Resolving server DNS ?

Similar Messages

Maybe you are looking for