Installation & Primary DNS Setup

During installation the Server Assistant app fills out the primary DNS based on the IP address supplied by my ISP. I want to use my own domain but when I click to change it Server Assistant gives a grave warning that network services may fail if I change it. So can I change it without worry? and do I need to get my ISP to remove any DNS records pertaining to my block of IP addresses? Should I be taking the mac mini server off the network during setup?
TIA
Joe

Certain services in Mac OS X Server are very dependent on DNS. If you're running Open Directory on this machine then you're in for a world of hurt if you change its DNS name.
If, on the other hand, you're just setting up the machine and haven't yet configured any services then feel free to change it - you've got nothing to break
As for your ISP's DNS, that depends on how you're running your DNS and your local network. In general if you're running your systems on a NAT network then I'd recommend configuring your own DNS server that knows all about your private addresses (e.g. your 192.168.x.x network) and leave your ISP out of the picture entirely (other than for public lookups of your public servers).

Similar Messages

Primary DNS Name: during Standard setup

Hi I hope you can help, I am installing Mac OS X Server via the Standard setup and all is going fine until I get to the point where it asks me to give the computer a name and underneath it displays the Primary DNS Name: currently it displays Bunnymen.config (Bunnymen being the name of my homenetwork device on my router), I believe that it should display standard.bunnymen.com (I own the name bunnymen.com along with a static ip address that the web address points to).
Do I need to set something up on my router first to show the correct address etc.
Any help would be great.
Thanks

OSX Server will get it's computer name from the reverse DNS lookup against the IP address. There is no forward address for either bunnymen.com or standard.bunnymen.com. Before proceeding, I would suggest that you fix the DNS names or you will start to have problems. You needs both forward and reverse addresses set up.

10.5 Server : Standard Installation : Newbie Tutorial / Setup Walk-Through

Hello all,
I recently setup OS X Server 10.5 for a client after doing it many times at my home. I could not have possibly done it without the help of this discussion board so thanks to everyone asking and answering questions!
To help other server newbies easily setup Server 10.5 (as apple claims), I'm hoping to make a basic installation procedure that will always work for newbies. Right now it's not exactly "detailed" - just the basic steps to ensure success.
Below is my setup procedure that has worked well for me (especially at my house). It's for a Standard installation; and we'll be setting up the server to include Mail (local only), iChat, VPN, File Sharing, iCal, Web Server/Wiki, Apple Remote Desktop access, and Time Machine (may not work well).
Please let me know if I'm missing something that will help ensure this setup works as perfectly as possible on any system.
+to help make sure this works, try using all the names i've used below (besides perhaps user names & passwords); like "server.house"+
*1) Setup Router*
• ensure router is properly connected to modem/internet
• router lan address = 10.0.2.1
• subnet mask = 255.255.255.0
• dhcp on
• dhcp server starts at = 10.0.2.9
• dhcp server ends at = 10.0.2.99
• dns server (opendns servers) = 208.67.222.222, 208.67.220.220 (not a completely necessary step, but may help ensure it works)
• port forward to 10.0.2.2 = vpn (udp: 500, 4500; udp/tcp: 50)
• port forward to 10.0.2.2 = ard (tcp: 5900, 5988; udp/tcp: 3283)
*2) Install/Setup Server*
• startup server computer with installation cd and start installation process
• choose "Standard Installation"
• setup administrator account with the following settings:
user name: Administrator
short name: admin
password: admin
• setup network settings (choose manual configuration):
manual ip address = 10.0.2.2
subnet mask = 255.255.255.0
router = 10.0.2.1
dns server = 10.0.2.2
search domain = house
• primary dns server = server.house
• server name = server
+choose all the services and let installation complete; wait until desktop loads+
Verify things are initially okay:
• Open safari, and type "server.house" in the address bar (ensure wiki appears)
Good, now:
• Download latest 10.5 server combo update, install, restart.
• Run software update until all updates are installed (may require several restarts)
• Setup a dyndns account for your server, install dyndns software (make sure it's updating via web and the ip address doesn't start with 10.x)
*3) Setup Server Preferences*
• open server preferences
• go to file sharing: turn on file sharing
• go to vpn: turn on vpn
shared secret = somethingsecretive
ip address range = 10.0.2.101 - 10.0.2.199
• go to users
• make new user(s) with all options enabled
+you should now have all services in server preferences enabled (if not, enable them) and user names setup; for good measure, restart the computer again+
*4) Setup Client Computers*
+make sure client computers have all software updates installed before proceeding+
• Open system preferences: network
• Make a new location called "Server"
• Set TCP/IP to DHCP
• DNS Server = 10.0.2.2
• Search domain = house
• Click apply
It's probably a good time to double check that the internet works - open Safari and google something. Good, it works.
There are two ways to setup the client computers to connect to the server with basically no manual configuration needed:
First way:
Go to system preferences: accounts: select user name to associate with server: select "server account" (if available): enter appropriate info for user on server: wait a bit: restart computer
or (if "server account" isn't available):
Second way:
Open finder: applications: utilities: directory utility. once opened, it should automatically find your server. if it doesn't, click the lock, click "plus sign", type = "open directory", server name = server.house, click ok
• enter appropriate info to connect to server and ensure it's set to automatically setup all services, once finished - restart.
*5) If the automatic setup didn't work, here's how to manually setup the client workstations:*
Safari
• Open Safari and type "server.house" in the address bar, enter user/pass, make sure it connects to wiki.
iChat
• add new jabber account
• jabber id = [email protected]
• server = server.house
• port = 5222
• kerbos = on (you can leave off if you want)
You can test by connecting to your Jabber account
VPN
• open Network in system preferences
• click lock
• click "plus sign"
• interface = VPN
• vpn type = L2TP over IPSec
• service name = server
• server address = your dyndns address
• click advanced
• dns server = 10.0.2.2
• search domain = house
• click ok
• click authentication
• enter user's server password
• enter "somethingsecretive" in "shared secret"
• click ok - click apply
You can test by clicking "connect" - after verified, disconnect.
_File sharing_
• Open finder: click "Server" under "Shared"
• If it connects as guest, click "connect as"
• enter your server username/password
Drag a file to and from a folder to make sure file sharing works
Mail
• Add new mail account (imap)
• Incoming mail server = server.house
• Outgoing mail server = server.house
• Outgoing authentication = kerberos 5 (or password)
• user name = [email protected]
• enter password
Check to make sure you get the server welcome e-mail and that you can send email to other users on the server.
*Time Machine* (very problematic at this time)
• Open Time Machine in System Preferences
• Click "options"
• Eliminate as many folders as possible to keep backup times shorter; click done
• Click "change disk"
• Select "Server" disk; click "use for backup"
** I highly recommend using local SuperDuper! backups and/or Retrospect for networked backups to the server. Other options include the dot mac Backup application or online backups (google it).
*If you have PCs on your network that you want to be able to connect to the server for file sharing*
• Open Windows Explorer (my computer)
• Click tools: map network drive
• Enter "\\server\public" (or if you setup a user account on the server for the pc user(s) i think you can use "\\server\pcusername" - and follow the next two steps)
-Click "connect using different user name"
-Enter pc user account username/password
• save settings
Check to make sure the drive shows up and you can move files to/from server
Helpful info for newbies setting up server 10.5:
• Apple's Server Resources page with all manuals
• Probably the most helpful newbie setup discussion
• Probably the most helpful newbie setup discussion #2
• Discussion about DNS
• "Time Machine is a dog... discussion"
• Manage Central Address Book discussion
• Leopard to Windows Files Sharing Issues discussion
• Lynda's 10.5 Server Training Videos (this does cost money and I haven't personally used it, but it looks very helpful)
I hope that's a good start for people, but I'm sure some setting(s) can be tweaked or I missed something that could make this process go even more smoothly. Lets make this the definitive newbie standard installation setup tutorial.
-Brian
corewerkz

Hi gikku,
Good idea! I forgot about the web server port forwarding, that will allow the wiki to be seen over the internet.
One question: what does adding the dyndns address to "Server Admin > web > settings > sites" actually do? I'm not too knowledgeable about Server Admin.
Thanks,
Brian
corewerkz

How to attach agent with unusual AD and DNS setup?

I am trying to configure DPM for a client, which is a university department. They have a somewhat unusual setup of their AD and DNS and I think that is why I am having trouble attaching an agent I have installed.
It is a new installation of DPM 2012 R2 version 4.2.1292.0 with a local SQL Server 2012 SP2. The OS is Windows Server 2012 R2. It is going to protect a bunch of SQL Server databases all on the same Windows Server 2012 R2 server. The SQL Server is a physical
server and the DPM server is a hyper-v VM, running on a Windows Server 2012 R2 host.
The install of DPM itself went smoothly.
To install the agent on the SQL Server machine, I followed the instructions here:
https://technet.microsoft.com/en-us/library/hh758186.aspx#BKMK_Manual. This was successful (I think)
Then I proceeded with these instructions to attach the agent:
https://technet.microsoft.com/en-us/library/hh757916.aspx
This fails at the enter credentials stage with this message:
DPM could not connect to the service control manager on these servers: [SqlMachinename].win.[universityname].dk (ID: 33221)
As far as I can tell, the problem has to do with how the university manages windows AD domains and DNS lookup.
The university uses one common AD domain named win.[universityname].dk for the entire campus, but it looks like DNS names for individual windows machines is managed locally at individual departments.
Ipconfig says this (abbreviated) for the SQL Server where I installed the agent:
Host Name . . . . . . . . . . . . : [SqlMachinename]
Primary Dns Suffix . . . . . . . : win.[universityname].dk
DNS Suffix Search List. . . . . . : win.[universityname].dk
[departmentname].[universityname].dk
Ethernet adapter T2:
Connection-specific DNS Suffix . : [departmentname].[universityname].dk
DHCP Enabled. . . . . . . . . . . : Yes
This works from the DPM machine and shows the correct IP:
ping [SqlMachinename]
This works from the DPM machine and shows the correct IP:
ping [SqlMachinename].[departmentname].[universityname].dk
This fails from the DPM machine ("could not find host") and does not get an IP:
ping [SqlMachinename].win.[universityname].dk
I've used Message Analyzer to verify that when pinging just [SqlMachinename], in fact DNS tries first to append win.[universityname].dk, which fails and second [departmentname].[universityname].dk, which then succeeds. This is by the book, as I understand
it because of the DNS Suffix Search list or because of the connections-specific DNS Suffix.
The problem is that DPM only tries [SqlMachinename].win.[universityname].dk. I have verified this with Message Analyzer.
I am not sure how to proceed. Is there another way to attach the agent? Maybe by IP-address?
I cannot ask the client to put [SqlMachinename].win.[universityname].dk in their DNS database. I am sure that they do not register any individual machines in that DNS domain which cuts across the entire campus. I am equally sure that they will not consider
creating individual AD domains for each department just because I ask (although that would probably be best in the long run).
Any suggestions would be very much appreciated.

Found a workaround:
I can install and attach the agent using one of the methods designed for agents in workgroups or untrusted domains. For me NTLM worked fine as long as I used simple nertbios computer names without any domain suffixes.
This is what worked:
On protected server:
SetDpmServer.exe -dpmServerName DPMServername -isNonDomainServer -userName DpmNtlmAccount
On DPM Server:
Attach-NonDomainServer.ps1 -DPMServername DpmServername -PSName servername -Username DpmNtlmAccount -Password xxxxx
I still think it is weird that DPM insist that protected servers in thewe same AD domain must use the AD domain name in their DNS name. Very inflexible.

Domain name/"primary DNS" name/mail host name/mail server name/mx name

Hi,
I have registered my domain name (N.com) with an external dns server and created an MX record (mail.N.com) for it as well. My server sits behind a router and internet traffic is port(80)-forwarded to my server's fixed internal ip address (I can access my webpages from the internet just fine). When I initially setup the server I was asked to give it a "primary DNS name." I naturally assumed that N.com was supposed to be entered here, but that just caused all kinds of problems (though I still do not understand why). So I reinstalled and currently have server.N.com as the primary DNS name of the server (although it shows up in Server Admin and Workgroup Manager as server.local--why is that?)
I have had no luck getting any email from the internet with the default settings in mail services (domain name of N.com and host name of server.N.com). Having no luck with the defaults, I assumed that maybe I needed to change the host name to "mail.N.com" so that it matched the MX record. I also changed the user preferences in Workgroup Manager to receive mail from mail.N.com--but still no luck. Could someone tell me what I am doing wrong and how come none of the Mail Service literature mentions anything about what a mail "host name" is supposed to be? Is it supposed to be the same as the "Mail Server" name that Workgroup Manager asks each user for? and is it the same as the MX record name?
I am just needing some help to connect all these variously named, but undefined, dots.
Also, how come I can access webmail from the internet using www.N.com/webmail but can't do it from any computers within my physical network (I have to use IPaddress/webmail or server.local/webmail)?
Also, should my user email addresses be [email protected] or [email protected] (which is the current default)?
Thanks in advance and good luck!
John

I had been told by a friend that ... regular email coming in from the internet would go through port 80
Unfortunately you were misinformed.
My MX record needs the extra subname (such as "mail") in front of the domain name, right?
Not at all. A MX record for 'N.com' is entirely valid (expected, in fact).
An MX record tells remote mail servers where to send mail for any domain/subdomain. If you think about it, let's say you worked for Apple and you wanted people to be able to send email to [email protected], well then you need an MX record for 'apple.com'.
You can see if you dig MX apple.com that they actually have 9 MX records, but the point still stands.
Now, you might also have MX records for subdomains so that you can have [email protected], [email protected], [email protected], etc. Each of these subdomains would need a separate MX record.
So, in general, for any set of email addresses @[anything.]domain.com you have a MX record telling remote mail servers where to send that mail.
Of course the MX record name is mail.N.com, but I think you are implying that the in the Mail settings of Server Admin where it asks for domain name all I need to put there is the N.com, right?
What I mean is that you need to set the domain name to whatever domain name you expect to receive mail at.
If you want users to have email addresses in the form of [email protected], then you enter 'N.com'.
If you want users to have email addresses in the form of [email protected] then you enter 'mail.N.com'.
If you want both forms, enter one in the main domain and add the other(s) in the Advanced -> Hosting -> Local Host Aliases section.
Is there anything in the Mail settings that needs to have the full MX record name (mail.N.com)?
Yes. Either the 'domain name' or the 'Local Host Aliases' needs to contain the same thing as your MX record. That's because the MX record tells remote servers to send mail to this machine, but the machine won't accept the mail unless it is configured to do so.
What is the "host name" supposed to be?
This should be the name that remote servers see when this machine tries to send outgoing mail.
Ideally this should match the reverse DNS of your IP address, that way when it connects to a remote server it says "Hi, I'm $hostname" and the remote server can lookup the machine's IP address and see the same result. This will reduce the problem of remote servers thinking you're sending them spam.
If you only have a single IP address then this probably needs to be something like 'N.com'. If you don't have control over your reverse DNS then you're going to run into a problem.
Also in the user accounts (in Workgroup Manager) what should the "mail server name" be? Is it the host name or the domain name?
Off hand, I don't know.
Also, why are all the default user email addresses [email protected] (the name I gave the server at setup)? Why doesn't the user accounts create [email protected] as the default address?
Presumably because the mail server says it is 'server.N.com' and therefore any accounts on that machine would be [email protected]. Changing the domain name (as above) should fix that.

DNS Setup/View external website internally

Greetings all - trying to set up a Mac server from scratch for the first time. Been managing one for a while but didn't actually set it up myself.
I have the beginnings of DNS setup all squared away, but am still looking to figure out how to properly set up my website. Here's my setup. We used to have a joint Windows 2003/10.5 server environment. Windows handled Exchange and DNS, the Leopard box handled everything else (DHCP, web, file sharing, etc). We're transitioning everything to the Mac box in preparation for setting up Kerio MailServer and just to ditch the windows box.
I own companyname.net - that domain is hosted externally by Network Solutions. It's forwarded to my static IP.
Our old internal DNS was hosted by a Windows 2003 box - it had zones for companyname.ltd (the private internal domain) and companyname.net. companyname.ltd was the nameserver. There were two A records handling the website for internal clients - one with a blank name, and one with www. Both pointed to the IP of the Mac server (the current box that I'm transitioning everything to). Everything was hunky dory - internal pings to the web address went to the internal ip, externally it went to the external IP, and everything worked just great.
So in setting up the new DNS on the Leopard box, here's what I have so far.
Primary zone: companyname.net
A Record: macpro : 192.168.1.3 (this is the name of the server)
A Record: mail : 192.168.1.2 (our mail server)
Alias : ichat : macpro.winstongroup.net
The checkhostname thing works fine, Kerberos is up and running, as is Open Directory.
Now, I do not know how to set up our website so that internal clients can view the external website. I tried creating an A record to the server for www, but then that overrides the macpro A record that is the host of the whole thing. I also tried creating A records to the external IP, but then when I pinged it just pinged once, then it seemed like the firewall kicked in and stopped it. I tried creating aliases to companyname.net but every time I did that, Server Admin kept adding on an additional companyname.net to the end of the name (so it would read like companyname.netcompanyname.net). That didn't make much sense to me.
I'm sure there's other people who can view internally hosted sites from the lan - so any help would be very much appreciated!

One minor other question. I prefer the url of our site to be companyname.net instead of www.companyname.net. So now, while www is set up as a server alias, it wouldn't direct to companyname.net, even though that URL was set up in the web services panel in Server Admin. I then created a new alias that was "companyname.net", without the trailing period so it was not a FQDM, directed it at the same web server, and everything seemed to work. Does that seem right - it's working, so it seems to be somewhat right at least!

Query on DNS setup for Active Directory for a new data center

I have third party DNS appliances providing DNS Service for Active Directory (Windows 2008 R2) and there are also secondary DNS servers, which are MS DNS server with a secondary zone configured, for redundancy. I have to setup a new data center
and move servers/services to this data center. In this scenario, can I install a new Microsoft DNS server with a secondary zone and use this as the primary DNS Server for all the member servers at this new location ? I am aware that this new DNS server will
not be able to make any updates to the secondary zone and for that purpose, is there anyway to redirect such requests to the DNS appliances in my current data center across the WAN ? I am trying to avoid purchasing a new DNS appliance for the new data center
and want to know what are the alternatives I have.

im not entirely sure by your setup, as normally you would use AD integrated zones for DNS in an AD environment - although there are other options as you have already setup.
the fact the zone is a secondary zone in DNS server terms doesn't mean you can't point your clients to it as their primary dns server. They will quite happily resolve names using a secondary server.
so as long as your dns devices are correctly setup to support the additional secondary zone I see no reason why you couldn't do this.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
My Blog
LinkedIn:

Secondary DNS failing to redirect clients when Primary DNS goes down

I have a single domain with two Windows 2008 servers, DC1 (physical) and DC2 (virtual). Both servers run DNS and are GC servers, and the entire domain is on the same subnet (192.168.0.x).
All clients on the network are configured to use DC1 as primary DNS, DC2 as secondary DNS.
DHCP is enabled only on DC1. (This might be part of the issue, not sure).
The problem is that when DC1 goes down for a reboot or repair, we lose access to the internet from our clients. Trying to pull up any website results in a "Page cannot be displayed" error. DC2 is available during this time and can be
pinged from any client but does not resolve DNS requests, even if I specify it as the primary DNS server on one of my workstations. However I can log on to DC2 locally and browse the web.
Here are the results of a DCdiag /dnsall from DC2 (I bolded areas of concern):
Directory Server Diagnosis
Performing initial setup:
   * Connecting to directory service on server DC2.
   * Identified AD Forest.
   Collecting AD specific global data
   * Collecting site info.
   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=mydomain,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
   The previous call succeeded
   Iterating through the sites
   Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=com
   Getting ISTG and options for the site
   * Identifying all servers.
   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=mydomain,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
   The previous call succeeded....
   The previous call succeeded
   Iterating through the list of servers
   Getting information for the server CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=com
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   Getting information for the server CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=com
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   * Identifying all NC cross-refs.
   * Found 2 DC(s). Testing 1 of them.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\DC2
      Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
Determining IP6 connectivity
* Active Directory RPC Services Check
......................... DC2 passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\DC2
      Test omitted by user request: Advertising
      Test omitted by user request: CheckSecurityError
      Test omitted by user request: CutoffServers
      Test omitted by user request: FrsEvent
      Test omitted by user request: DFSREvent
      Test omitted by user request: SysVolCheck
      Test omitted by user request: KccEvent
      Test omitted by user request: KnowsOfRoleHolders
      Test omitted by user request: MachineAccount
      Test omitted by user request: NCSecDesc
      Test omitted by user request: NetLogons
      Test omitted by user request: ObjectsReplicated
      Test omitted by user request: OutboundSecureChannels
      Test omitted by user request: Replications
      Test omitted by user request: RidManager
      Test omitted by user request: Services
      Test omitted by user request: SystemLog
      Test omitted by user request: Topology
      Test omitted by user request: VerifyEnterpriseReferences
     Test omitted by user request: VerifyReferences
      Test omitted by user request: VerifyReplicas
      Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
See DNS test in enterprise tests section for results
......................... DC2 passed test DNS
   Running partition tests on : ForestDnsZones
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running partition tests on : DomainDnsZones
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running partition tests on : Schema
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running partition tests on : Configuration
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running partition tests on : mydomain
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running enterprise tests on : mydomain.com
      Starting test: DNS
Test results for domain controllers:
DC: DC2.mydomain.com
Domain: mydomain.com
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
                  Microsoftr Windows Serverr 2008 Standard
(Service Pack level: 2.0)
is supported
NETLOGON service is running
kdc service is running
DNSCACHE service is running
                  DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000006] Intel(R) PRO/1000 MT Network Connection:
MAC address is 00:0C:29:91:59:68
IP Address is static
IP address: 192.168.0.249
DNS servers:
192.168.0.105 (DC1.mydomain.com.) [Valid]
127.0.0.1 (DC2) [Valid]
The A host record(s) for this DC was found
Warning: The AAAA record for this DC was not found
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.) - mydomain.com]
                  The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders Information:
192.168.0.105 (DC1.mydomain.com.) [Valid]
192.168.0.7 (<name unavailable>) [Invalid (unreachable)]
Error: Forwarders list has invalid forwarder: 192.168.0.7 (<name unavailable>)
TEST: Delegations (Del)
Delegation information for the zone: mydomain.com.
Delegated domain name: _msdcs.mydomain.com.
DNS server: DC1.mydomain.com. IP:192.168.0.105 [Valid]
TEST: Dynamic update (Dyn)
Test record _dcdiag_test_record added successfully in zone mydomain.com
Test record _dcdiag_test_record deleted successfully in zone mydomain.com
TEST: Records registration (RReg)
Network Adapter
[00000006] Intel(R) PRO/1000 MT Network Connection:
Matching CNAME record found at DNS server 192.168.0.105:
a32fcfbd-16bb-4697-a23d-20fc3b8c274c._msdcs.mydomain.com
Matching A record found at DNS server 192.168.0.105:
DC2.mydomain.com
Warning:
Missing AAAA record at DNS server 192.168.0.105:
DC2.mydomain.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.ac09921d-4553-475e-b25c-059742ac0552.domains._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._tcp.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._udp.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kpasswd._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_kerberos._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.gc._msdcs.mydomain.com
Matching A record found at DNS server 192.168.0.105:
gc._msdcs.mydomain.com
Warning:
Missing AAAA record at DNS server 192.168.0.105:
gc._msdcs.mydomain.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Matching SRV record found at DNS server 192.168.0.105:
_gc._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.105:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.mydomain.com
Matching CNAME record found at DNS server 192.168.0.249:
        a32fcfbd-16bb-4697-a23d-20fc3b8c274c._msdcs.mydomain.com
Matching A record found at DNS server 192.168.0.249:
DC2.mydomain.com
Warning:
Missing AAAA record at DNS server 192.168.0.249:
DC2.mydomain.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.ac09921d-4553-475e-b25c-059742ac0552.domains._msdcs.mydomain.com
             Matching
SRV record found at DNS server 192.168.0.249:
_kerberos._tcp.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kerberos._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kerberos._udp.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kpasswd._tcp.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
           Matching
SRV record found at DNS server 192.168.0.249:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_kerberos._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.gc._msdcs.mydomain.com
Matching A record found at DNS server 192.168.0.249:
gc._msdcs.mydomain.com
Warning:
Missing AAAA record at DNS server 192.168.0.249:
gc._msdcs.mydomain.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Matching SRV record found at DNS server 192.168.0.249:
_gc._tcp.Default-First-Site-Name._sites.mydomain.com
Matching SRV record found at DNS server 192.168.0.249:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.mydomain.com
Warning: Record Registrations not found in some network adapters
TEST: External name resolution (Ext)
Internet name www.microsoft.com was resolved successfully
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.0.7 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.168.0.7
[Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 192.168.0.105 (DC1.mydomain.com.)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS delegation for the domain _msdcs.mydomain.com. is operational on IP 192.168.0.105
DNS server: 192.168.0.249 (DC2)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
Domain: mydomain.com
DC2
PASS WARN FAIL PASS PASS WARN PASS
......................... mydomain.com failed test DNS
      Test omitted by user request: LocatorCheck
      Test omitted by user request: Intersite

Looks like it may be trying to forward to a machine that's down (DC1 and another 192.168.0.7) and root hints aren't available.
Check out this article:
http://technet.microsoft.com/en-us/library/ff807391(v=ws.10).aspx
See if you can enable DNS access through the firewall to the Internet if it's not already available. Try to match whatever forwarder settings are on DC1, or remove them entirely and let the server resolve DNS from Internet root servers. Alternativly,
you could change your forwarder to a public DNS server you have access to, your ISP should supply this or you could test with something common like 4.2.2.2.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Multiple Leopard Servers - DNS Setup

Hi guys,
Just wandering what I need to do when setting up more than one server on the network with my DNS settings.
I already have a leopard server box, running advanced with DNS setup and working correctly. How do I setup the second server?
Do I create a machine record on the original server, as if the new server is just another network device, and not turn on dns on the new server?
Thanks,
Nige

"If you like you can add a NS record for the new machine/DNS name, set the new machine up as a secondary/slave DNS and allow for zone transfers in the first primary/master one. "
hmm, I think I follow.
"The second one should use the same forwarders as the first one (both machines should only use itself as the DNS in Network prefpane) and also the LAN reverse zone (*.in-addr.arpa.) should be zone transfered to the secondary DNS."
Are there instructions on setting up a secondary DNS?
"In DHCP setup also add the second machine/DNS IP so clients can use either/both."
I'm not running DHCP on the server, so I'm not sure what I can do here.
I guess I'll need to do a similar thing with directory as a well, so that both servers have the same users and groups.
Nige

Primary DNS server

Hello,
I am trying to setup a local primary dns server that will resolve local server names but at the same time forward request that it doens't have.
like i would like it to resolve our internal web address and still pull up google.com. I put in about ten records and all those work but when i try anything else it doesn't work. Can someone help?
Thanks,
Jay

What's different about 10.4.9 in this
case?
10.4.9 update "Addresses slow performance of non-cached DNS queries and provides an update to BIND version 9.3.2."
You may still prefer to add forwarders but, taking above on face value, no longer necesary for those who do not want to manually edit files.
Mind you, I have not actually tested the default DNS in 10.4.9 so cannot confirm that the previous problems do not still occur (but just to a lesser extent .
-david

GSS as primary DNS Server for Intranet

Hi,
Can the GSS be used as a as primary DNS server for Intranet? An additional DNS server can be configured to answer the unknown Records like MX by GSS.
if it can be configured, I would be thankful if anyone shares with me the brief configuration steps Apart from configuring Answers, answer groups, domain lists, source address lists, DNS rules.
with thanks
sathappan

Yeah I'd certainly recommend against it! So essentially the client machines are unable to update or query dynamic AD related DNS records since they're not pointing to the DNS servers actually used by your AD server(s). I could well imagine that causing
issues, and meaning that some AD functionality won't work correctly.
I know you can directly integrate BIND with AD, eg so that the BIND servers are the ones used by AD, though I haven't tried it, but this seems to be neither.
I can't find any articles relating to your exact situation, presumably no one else has tried to use such a mixed and disjoined setup. I'd focus on looking for articles relating to why you shouldn't point your users at a router (most commonly in small setups
on ADSL) for the DNS rather than directing them to the server for DNS and then having that query the router for external results. It's a more common scenario and you're more likely to find articles relating to it.
One article you might find useful is
http://msmvps.com/blogs/acefekay/archive/2009/08/17/ad-and-its-reliance-on-dns.aspx which talks in terms of using your ISP's DNS servers on the client machines, but in your situation it sounds like the BIND servers are essentially providing an equivalent
setup.
There's also various discussions and comments on the topic elsewhere on these forums, for instance
http://social.technet.microsoft.com/Forums/windowsserver/en-US/c3ba3859-765e-4b3f-add0-eaf2c18e1068/i-have-dns-in-a-router-and-i-want-to-install-domain-controller?forum=winservergen and
http://social.technet.microsoft.com/Forums/windowsserver/en-US/b5df8fd4-7ab2-4d1e-afe2-c5263c4d69c3/dns-server-forwarding-and-clients-getting-address-of-registrars-ip?forum=winserverNIS which are worth checking out.

Set Primary DNS Suffix Using Powershell

For a Windows Server 2012 installation, what Powershell cmdlet can be used to change the Primary DNS Suffix ? I've tried using 'Set-DnsClientGlobalSetting -SuffixSearchList contoso.com' but this only alters the DNS Suffix Search List, not the primary DNS
suffix.

You might want to take you question to one of two forums that specialist in scripting issues.
For PowerShell specific questions -
http://social.technet.microsoft.com/Forums/en-US/home?forum=winserverpowershell
For general scripting questions -
http://social.technet.microsoft.com/Forums/en-US/home?forum=ITCG
They have a lot of really sharp scripting people in those forums.
.:|:.:|:. tim

How do I find my Primary DNS with a wireless router?

My PS3 keeps asking me for my primary DNS, but I can't find it.

It is optional, but as Duane has suggested you can substitute the OpenDNS DNS server IPs for both the primary & secondary DNS servers. So, for example, you can enter: 208.67.222.222 for the primary and 208.67.220.220 for the secondary instead of x.x.x.1 that you are using now.

Help with Proper DNS Setup for Leopard Standard Server Setup

Hello All,
Problem Description-
I was reviewing some training today on DNS setup and checking for proper setup with the sudo changeip - checkhostname tool and I seem to have an incorrectly configured DNS setup. So I need some help on correcting it. When I go to the "Server Preferences" tool I cannot log in using apple.ourdomainname.com instead in order to use the tool I have to input localhost as the server name. Now I just thought that the system was broken or something and with the help of my training I now see it's a DNS problem. I thought I had everything proper since I followed the steps of creating proper DNS/RDNS entries with my ISP. Now I am stuck wondering what else isn't working properly due to the DNS issue. Thanks in advance.
Technical Info-
My ISP provides us with 5 static IP's and we have asked them to create entries and verified the setup of apple.ourdomainname.com = x.x.x.x which is one of our public IP's assigned currently assigned to the WAN port of our Apple Airport Extreme. We have also had them create a PTR record which also is present, verified and functional. Our MacMini running 10.5.5 is connected directly to one of the ethernet ports on our Apple Airport Extreme which is our NAT/Firewall for the LAN. So during the setup of the Standard Server install the OS configured the Airport with the required ports for chat/web/vpn. And mobile Mac's can VPN in and gain folder access and web works fine too. We don't use the e-mail portion so I can't say how that works. The server is using the DNS of 10.0.200.1 which is the IP of the Airport and the airport is programmed with the DNS of OpenDNS servers 208.67.222.222 and 208.67.220.220. The reason for this whole long shpeal is that I want to give as much technical background as possible for the best possible help.
Thanks
DM

What happens when you use 'Localhost' instead of 'localhost' (i.e. capitalizing the 'L')?

WAP200 and entry for primary dns cannot be 0 and 255

I have a wap200 with a static ipaddress e.g. 192.168.249.205/24 (it is for management and is in vlan 1). Firmware of the wap is 2.0.4.0. No gw and no dns. (they are not necessary) I export the config . I have a second wap200 and import the config.bin to the new wap. ThenI like to change the static address and the name of the new wap, but - and this is the problem - it asks me to fill out the dns (the address for primary dns cannot be 0 and 255), but I absolutely don't want that because there is no dns or gw (management only). And if I fill it out I cannot go the the internet with the wap.
So I also have some other wap200 where I could import the config.bin and change the static ip without giving a dns (firmware 2.0.1.0).
So my question is: can I go back to a previous firmware (Europe) and where can I find it. Looked for it, but seeing only the last one 2.0.4.0 etsi.
Or is there another method to skip the dns with a static ipaddress?
many many thanks in advance.
Kurt

Hello Stephanie,
If you’ve received this mail twice, you can delete one of them. It was not the intention.
Best regards,
Kurt Stichelmans
Goodmorning Stephanie,
First a great thanks for replying to my question.
For explaining my situation I ‘ll try to give you a full view.
I have 3 vlans configured on the network through a Motorola wireless ws5100 switch . Vlan 1 (192.168.249.xxx/24): management, vlan 2 (172.20.176.xxx/24): for the public, vlan 3(10.63.128.xxx/20): for internal users only.
I have 4 wap200 configured of which one is having trouble. I configured the other three as follow: starting, connecting, giving it an ipaddress in the management vlan and upgraded the firmware from version 2.0.1 to 2.0.4. When I connect to the wireless ssid “public” I get an ipaddress from the range 172.20.176.x. When I connect to the ssid “internal users” I get an ip from the range 10.63.128.x and when I connect to the ssid “management” I get an ip from the range 192.168.249.x. The last one is only for management so I can not go to the internet from here (which is ok), from the other two I can go to the internet as wished and the two ssid’s can not communicate which each other as wished.
Important: the ipaddress of the wap200 has an ipaddress 192.168.249.200/24 with no dns input (no dns is needed so..)
With the fourth one I did first a firmware upgrade and I imported the config of another wap200 (one of the first three). Then I wanted to reconfigure the wap (ipaddress) but when I change the ipaddress and click on save I have to give also a dnsentry. (When I do this with the other wap200 it’s asking me also a dnsentry, so it must be the firmware). When I give a dns entry I cannot go to the internet with ssid “public” nor “internal user”.
So what I thought is to go back to firmware 2.0.1 and then import the config of another wap200. So I can change the ipaddress without the need of a dnsentry. After that I can upgrade to the last firmware. And job done.
Hope you can help me to make the situation usable.
Kind regards
Kurt Stichelmans

Installation & Primary DNS Setup

Similar Messages

Maybe you are looking for