DNS Name in OD Password Server field?

So, I got a new juniper firewall the other day to reduce the amount of work my main server has. Fire it up, configure it, and I notice that password server requests are going out the NAT, then back into the public IP of the server.
My question is this: would it be wise and/or acceptable to change the IP address to a URL in OD (in WGM, Click on target, config in the popup, passwordserver in the list, value in question is PasswordServerLocation and dsAttrTypeNative:apple-password-server-location)?
I would rather do this as the internal DNS points the proper name to the internal IP, while the external does the same for the public IP, so password server would work properly no matter where a user is.

Hi,
johan wrote:
> Is it possible to put a DNS name in an Exception filter ?
No.
> And can i open a filter for a range of destination addresses like 10.0.6.*
Well, sure. You use a Network as destination (vs. a HOST).
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

Similar Messages

Leopard Server Assistant and DNS Name

I am trying to setup Leopard Server in my home...
Server assistant launches I fill in the information and everything is fine... except I do not know what to put in the Server DNS name box. If I leave as is the server tools do not start because they cannot resolve the machine name.
In short what is going on...
1. How do you change the machine DNS name after server assistant has finished running?
2. What should I put in the DNS box?
MACServer.local? or MACSERVER
3. If I move to Dynamic DNS how do I change this later without having to re-install.
I have to admit that setting the server up, installing disks was easy but the DNS issue seems to be a real stumbling block for setting up a home server.
What am I doing wrong?
Message was edited by: Peter Jarvis
Message was edited by: Peter Jarvis

Tony,
Thanks for the response.
My concern is that a normal home user will not be able to setup MAC Server 10.5 very easily without knowledge of DNS. (I will walk through a setup later on in the mail)
My point is that the average user will not be able to setup MAC Server. They will have difficulty filling out the setup wizard correctly - for this reason I cannot recommend it to a rookie. What is needed is a really simple setup scenario script that can be given to user so they can setup a MAC server in the home to support file sharing, intranet web browsing and time machine backups and central storage for users.
Don't get me wrong a MAC admin will find the changes in 10.5 a significant and fine improvement over past mac server setups and a leap frog over the Windows and Linux setup experience. Don't let anyone persuade you that Microsoft Home Server is a easy either. (Actually corrupts data with certain apps) - great testing Microsoft
Back to good software...
MAC Server Setup example: (Newbie the new IT for the household)
Prior to setting up the server Newbie will need to define his system setup...
i.e.
Server Name [email protected]
IP Address: 192.168.0.100
Router: 192.168.0.1
Is the machine going to be a gateway or behind a firewall?
Will it distribute IP addresses for the home network etc?
These points are important as the DHCP and DNS go hand in hand. If the router is acting as a DNS relay and handing out IP addresses this may interfere with setting up the server to be primary DNS provider in the home.
Walkthrough 1: Scenario:
Setup the server to be a simple server with only file sharing, web server and time machine.
When asked Newbie enters:
Domain name: pkjserv.technophobic.com
Server Name:192.168.0.100 (DHCP) or manual
Nebie configures the server...
after setup the first thing that will happen is that Server Preferences will launch it will populate with the above server data...
Problem: Newbie trys to use server preferences and types in his password and fails to get access...
Why... because Server preferences expects "pkjserv.technophobic.com" to resolve but DNS is not setup yet...
OK so Newbie needs to setup DNS...
Newbie selects Applications/Server/Server Admin.app
(Newbie uses Magic to find Server Admin)
First prompt "Are you sure you want to use Server Admin?"
Newbie selects "Use Server Admin"
(Newbie uses Magic to know he has to do this)
Connect to server via IP address 168.192.0.100
Select DNS add click to box...
Expand 192.168.0.100 (our server)
Select DNS
Select zones...
Add primary zone / Select example.com
Change Primary zone to "technophobic.com."
Select "ns" and Change Nameserver to "pkjserv"
Under primary domain select machine change machine name to "pkjserv"
Select IP Addresses and change to 192.168.0.100
Click "save"
Newbie should have the following setup displayed:
Name Type Value
technophobic.com Primary Zone -
pkjserv Machine 192.168.0.100
0.168.192.in-addr.arpa Reverse Zone -
192.168.0.100 Reverse Mapping pkjserv.technophobic.com
------- Start DNS...
The problem here is that DNS is working but Newbies IP setup is still not referencing the DNS server so newbie will have to add it to the network settings.
Preferences / Network / advanced / DNS
once they have done this Newbie should be able to launch your browser and type "pkjserv.technophobic.com" and have it resolve to the web browser on the machine...
in short - this is difficult... hence my proposal that Apple need to create a simple setup scenario scripted document (fill in blanks) so a user can setup a MAC server in the home. Current docs do not allows an average user to install MAC OSX Server - I want a simple MAC Server that anyone can install...
Pete
Message was edited by: Peter Jarvis

Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."

Hi,
Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."
DC:windows Server 2008 R2
Domain functional level:Windows Server 2003
When Winxp join domain, have no this error message.
I checked http://support.microsoft.com/kb/2018583?wa=wsignin1.0 does't work.
There have 3 suggestion in this article:
1.The "Disable NetBIOS over TCP/IP" checkbox has been disabled in the IPv4 properties of the computer being joined.
Doesnt's work.
2.Connectivity over UDP port 137 is blocked between client and the helper DC servicing the join operation in the target domain.
On my DC, I run netstat -an, reslut as below:
UDP 192.168.20.3:137 *:*
3.The TCP/IPv4 protocol has been disabled so that the client being joined or the DC in the destination domain targeted by the LDAP BIND is running TCP/IPv6 only.
We are not using IPV6.
This server recently updated from Windows Server 2003 to Windows Server 2008 R2. Before upgrade, when Win7 and Win2008 join this domain, also have the same error message.
Please help to check this issue.
Thank you very much.
BR
Guo YingHui

Hi Guo Ying,
I have faced this critical error which makes over-writes the host names in the domain when you join.
For example: Already you had a host name called as PC.domain.com in the domain.com Domain.
When you try to add the another host name called as PC in the domain.com Domain, it doesn't give you the duplicate name error on the network it does over-write the existing host name called as PC.domain.com & it will add the new host name into the domain.
Host name which got over-written will get removed from the domain. I faced this issue in my project. My DPM host name got removed from the Domain & new host name got joined into the domain which halted my backups for one day.
Final Resolution is as follows:
You need to start the dns console on the DC & drop down the domain name.
Select the _msdcs when you click on _msdcs it will show the Name Server's list on the right hand side.
You need to add the Domain Naming Master under the _msdcs or add all the domain controllers which you had.
After you add the Name server's try joining the PC OR Laptop to the domain which is successfully joins it.
Regards
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

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.

Error cannot connect to server or DNS name when working with the SRDemo

I receive the error cannot connect to server or Dns name when trying to
display the SRlist.jspx page in the SRDemo. I am using the embedded OC4J server . I tried to using the debugger to trouble shoot the problem but I did not get any information that was useful. The url I am using is http://localhost:8989/SRDemo-UserInterface-context-root/faces/app/SRlist.jspx I also tried using the IP address that didn't work . I really need to get through this demo.

What about using:
http://127.0.0.1:8989/SRDemo-UserInterface-context-root/faces/app/SRlist.jspx
Or disabling any proxy settings your browser might have?

Alias with field name in MS SQL Server

Is it possible that we can define alias for field name in MS SQL Server?
For example:
mytable : Id, Name, Value
Could we define "AnotherName" for "Name" field that we can call it from sql
SELECT anothername from mytable

I don't know if you can "permanently" create an alias
without a view or something like that but if you just
want another name when you execute a select do this:
Select name as another name from tableAt least in some databases the syntax for that can vary slightly. So the following might be needed....
Select name as 'another name' from table

[10.6 Server]Strange DNS Name

Hi,
I'm having a strange (local) hostname on my XServe, running Snow Leopard Server 10.6.1.
When I view the DNS Name in the 'Server Preferences, Information-view', it shows: xserve-002436f2bc56.local
I see the same name as a prompt when I start the terminal.
How can I set (and save) the hostname of my Snow Leopard Server?
- I've set the hostname in the PreferencesPane 'Sharing' to xserve01
- I've set the hostname in the Terminal, using the command 'hostname' to xserve01.going.nowhere. (fully qualified domainname in our local domain)
- I'm running DNS Server on this machine, and both the A-record and the PTR-record are set correctly: 192.168.0.111 <-> xserve01.going.nowhere
Just to be complete:
OS: Snow Leopard Server 10.6.1
Services: Only Bind
IP: 192.168.0.111
DNS1: 192.168.0.111 (itself)
BTW: When I set the hostname in the terminal, but sort of saves that hostname as long as the server is up. But it doesn't change the DNS Name shown by "Information" in the Server Preferences.app.

That is the default name if you do not specify one at setup, which is your HW Type and MAC Address.
To change, open Server Admin, highlight your server, then click the the Settings Tool button, then select the Network button. You will see xserve-002436f2bc56. Change it there.
OR
`sudo /System/Library/ServerSetup/serversetup -setComputername NEWNAMEHERE`
Peter

How can i change the DNS Name of a 10.6 Server

Hello when i installed the Server i made a mistake and put in a wrong dns name wich is not reachable from the clients. How can i Chane the DNS Name?

The core command is changeip, and Google will find some details and discussions.
$ man changeip
$ changeip {-v} {-d path} directory-node old-ip new-ip {old-hostname new-hostname}
It's not always successful; the host name tends to get embedded everywhere.
For the official documentation on this, see the [Advanced Server Management Manual|http://manuals.info.apple.com/enUS/ServerAdminv10.6.pdf] for a discussion of what (else) needs to happen when the IP settings change; see the +Understanding Changes to the Server IP Address or Network Identity+ section.

ICloud asked me to reenter my password to get mail and when I did, it rejected my password. I'm trying to reenter in my account information, but it won't let me because the incoming mail server field is blank, but it won't allow me to enter anything.

iCloud asked me to reenter my password to get mail and when I did, it rejected my password. I'm trying to reenter in mail account information, but it won't let me because the incoming mail server field is blank, but I can't enter anything into that field.

No, didn't have to sign out. As I started to, got a messge saying something about losing all my calendar information, which unnerved me so I didn't sign out. It was correcting the password in another email account that corrected the situation for me.

DNS Name field empty - why?

Hi all,
Please forgive my naive question, I am not a guru of networking...
I am trying to understand why the Macs in my network (10.4.9) always have their DNS name field in ARD 3.1 empty ("Unknown") whereas the PCs (although obviously not accessible with ARD) do show up with their DNS name.
I can edit each computer "info" window, but I am not quite sure that's the way it should be done.
What do I have to do in order to know and see the DNS name?
Isn'it it supposed to be the (Mac) computer's name.local ?
Many thanks for your attention.
Cheers
Carlo
Powerbook 12 Mac OS X (10.4.9)
Powerbook 12 Mac OS X (10.3.9)
Powerbook 12 Mac OS X (10.3.9)
Powerbook 12 Mac OS X (10.3.9)

It sounds like your user account is not in the admin group. Open System Preferences -> Accounts and check that there is at least one admin account. If none of those accounts are listed as admin accounts, see here for a fix: http://discussions.apple.com/thread.jspa?threadID=1323191&tstart=0

ACE 4710 use dns name in real server

Is there any way to use a DNS name in real server and not a static IP.

Hi,
This is not possible at the moment. With ACE EOL, i don't think it would be added either.
Regards,
Kanwal
Note: Please mark answers if they are helpful.

Unity Express Backup: Can we use DNS name of FTP server instead of IP address?

Gentlemen!
In the Unity Express system, can we use DNS name of FTP server (Microsoft FTP Server) instead of IP address in the General configuartion for Backup Server?
e.g. FTP://FTP_Server_Name/Directory
Additionally we need to configure/add DNS server name in the Domain Name settings under system menu. Is there any additional configuration would require for setting up FTP server with DNS entry & above config?
Regards,
Sky_Voice

Hi Sky_Voice,
This is a supported config
Backing Up and Restoring Data
Last Updated: May 12, 2010
Cisco Unity Express backup and restore functions use an FTP server to store and retrieve data. The backup function copies the files from the Cisco Unity Express application to the FTP server and the restore function copies the files from the FTP server to the Cisco Unity Express application. The FTP server can reside anywhere in the network if the backup and restore functions can access it with an IP address or hostname.
We recommend that backups be done regularly to preserve voice-mail messages and configuration data.
Backup and restore commands are available in configuration mode and in offline mode.
•In configuration mode, commands are available to set the following parameters:
–Number of backup files to keep (the oldest file is deleted).
–URL of the FTP server where the files will be stored.
•In offline mode, perform the backup or restore procedure. Decide the following:
–Type of files to be backed up: all files (configuration and data), only configuration files, or only data files. Data files consist of voice-mail messages. Configuration files consist of all other system and application parameters.
–URL of the FTP server where the files will be stored.
http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/rel3_2/administrator/voicemail/11bkrst_ps5520_TSD_Products_Administration_Guide_Chapter.html
Cheers!
Rob

Error: Missing SRV record at DNS server - [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]

in an attempt to transfer FSMO roles to the 2012r2 DC the first thing I ran was dcdiag /e /c /v and after correcting some minor errors, I came upon this one in the DNS portion where a SRV record is missing and I have no idea how to fix/remove this. there's
only two DCs, 200.5 and 200.6 where the former is a Hyper-V VM running 2012r2 and the latter is a physical 2003r2 machine. I was able to successfully raise the levels to 2003 and join the 2012r2 DC. this missing SRV record does not look fatal and only warrants
a warning from dcdiag, however I would like to fix this so there's no trouble down the road. I've tried ipconfig /registerdns, but no dice. here is the message I'm concerned about:
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
the bottom portion of the DNS section that contains this message is in the RReg section and is as follows:
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
Matching CNAME record found at DNS server 192.168.200.5:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
CM-DC1-HV-NYC01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.6:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
CM-DC1-HV-NYC01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters

Hi Ace Fekay, thank you for your help. I hope you're still with me despite my lack of responding. I needed time to move the VPN server from the DC to a separate VM and then following your instructions to disable WINS Proxy and IP routing. Some of the delay
was when I had to restart the 2003r2 server after disabling those two items since that cause DNS queries to the Internet to go unresolved with only the 2012r2 server. That's been corrected, but running dcdiag /c /e /v still gives some DNS problems. Here's
the latest run of that...
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
Starting test: DNS
See DNS test in enterprise tests section for results
......................... CM-DC-NY01 passed test DNS
See DNS test in enterprise tests section for results
......................... CM-DC1-NY01 passed test DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : cmedia
Starting test: CheckSDRefDom
......................... cmedia passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... cmedia passed test CrossRefValidation
Running enterprise tests on : cmedia.local
Starting test: DNS
Test results for domain controllers:
DC: cm-dc-NY01.cmedia.local
Domain: cmedia.local
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS Microsoft(R) Windows(R) Server 2003, Standard Edition (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 [00000001] HP NC373i Multifunction Gigabit Server Adapter:
MAC address is 00:00:00:00:00:00
IP Address is static
IP address: 192.168.200.6
DNS servers:
192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
192.168.200.5 (CM-DC1-NY01) [Valid]
The A host record(s) for this DC was found
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 are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
TEST: Delegations (Del)
Delegation information for the zone: cmedia.local.
Delegated domain name: _msdcs.cmedia.local.
DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
Matching CNAME record found at DNS server 192.168.200.6:
406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
cm-dc-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.pdc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.5:
406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
cm-dc-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.pdc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters
DC: CM-DC1-NY01.cmedia.local
Domain: cmedia.local
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS Microsoft Windows Server 2012 Standard (Service Pack level: 0.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 [00000010] Microsoft Hyper-V Network Adapter:
MAC address is 00:00:00:00:00:00
IP Address is static
IP address: 192.168.200.5, 0000::0000:0000:0000:0000
DNS servers:
192.168.200.5 (CM-DC1-NY01) [Valid]
192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
The A host record(s) for this DC was found
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 are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 128.9.0.107 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
Name: d.root-servers.net. IP: 128.8.10.90 [Invalid (unreachable)]
Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unreachable)]
Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreachable)]
Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unreachable)]
Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreachable)]
Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
TEST: Delegations (Del)
Delegation information for the zone: cmedia.local.
Delegated domain name: _msdcs.cmedia.local.
DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
Matching CNAME record found at DNS server 192.168.200.5:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
CM-DC1-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.6:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
CM-DC1-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters
Summary of test results for DNS servers used by the above domain controllers:
DNS server: 198.32.64.12 (l.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12 [Err
or details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:1::803f:235 [Error details: 1460 (Type: Win32 - Description: This operation ret
urned because the timeout period expired.)]
DNS server: 2001:500:2::c (c.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2::c [Error details: 1460 (Type: Win32 - Description: This operation returned b
ecause the timeout period expired.)]
DNS server: 2001:500:2d::d (d.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2d::d [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:84::b (b.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:84::b [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:503:ba3e::2:30 [Error details: 1460 (Type: Win32 - Description: This operation retu
rned because the timeout period expired.)]
DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:503:c27::2:30 [Error details: 1460 (Type: Win32 - Description: This operation retur
ned because the timeout period expired.)]
DNS server: 2001:7fd::1 (k.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:7fd::1 [Error details: 1460 (Type: Win32 - Description: This operation returned bec
ause the timeout period expired.)]
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90 [Erro
r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 128.9.0.107 (b.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.9.0.107 [Erro
r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2f::f [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:3::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:3::42 [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:7fe::53 [Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:dc3::35 [Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
DNS server: 128.63.2.53 (h.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.112.36.4 (g.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.168.200.5 (CM-DC1-NY01)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS server: 192.168.200.6 (cm-dc-NY01.cmedia.local.)
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.cmedia.local. is operational on IP 192.168.200.6
DNS server: 192.203.230.10 (e.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.228.79.201 (b.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.33.4.12 (c.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.36.148.17 (i.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.5.5.241 (f.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.58.128.30 (j.root-servers.net.)
All tests passed on this DNS server
DNS server: 193.0.14.129 (k.root-servers.net.)
All tests passed on this DNS server
DNS server: 198.41.0.4 (a.root-servers.net.)
All tests passed on this DNS server
DNS server: 199.7.83.42 (l.root-servers.net.)
All tests passed on this DNS server
DNS server: 199.7.91.13 (d.root-servers.net.)
All tests passed on this DNS server
DNS server: 202.12.27.33 (m.root-servers.net.)
All tests passed on this DNS server
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
Domain: cmedia.local
cm-dc-NY01 PASS PASS PASS PASS PASS WARN n/a
CM-DC1-NY01 PASS PASS PASS PASS PASS WARN n/a
......................... cmedia.local passed test DNS
Starting test: LocatorCheck
GC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
PDC Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
Time Server Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
KDC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
......................... cmedia.local passed test LocatorCheck
Starting test: FsmoCheck
GC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
PDC Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
Time Server Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
KDC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
......................... cmedia.local passed test FsmoCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
provided.
......................... cmedia.local passed test Intersite

Getting single "generic" WLS 4.5.1 app to serve multiple DNS names, including SSL

Hi everybody,
I am trying to figure out a strategy to enable a single web application
based on WLS 4.5.1 (SP13) running on Linux to serve multiple DNS
names, with some specific pages to be transmitted using SSL.
While the JSP pages differ in colouring and screen layout (but not in
logic),
the entire EJB business logic is identical for all DNS names. So are the
servlets.
The application data to be presented to the user can easily be mapped,
and presently (with the application responding to a single DNS name)
it is cached using a JNDI tree. To minimize coding effort, and
to continue utilizing the present caching concept, only expanding it to
support
multiple similar "virtual" applications, I would prefer to
continue using a single WLS instance when making the application "generic".
But as a consequence of this, I could only present a single SSL certificate
to the user if I had WLS answer internet HTTP requests directly.
What would you think should be done to get the browsers
"display the closed padlock while in the order form" for multiple DNS names
served by this same application instance?
One approach might be to put Apache in front of WLS, and configure it
to serve multiple virtual hosts (one for each DNS name to be served,
encoding the differences between the request URLs somehow in the ServerPath
directive, and providing a separate SSL certificate for each of those
virtual
hosts).
Does this make sense to you? Any experience in this area? Which Apache
and WL modules should I be using - which combination
of mod_proxy, mod_ssl (by Apache), mod_wl, mod_wl_ssl[_raven] ?
Any input would be greatly appreciated! Thanks in advance!
Ruben
[A minor add-on question is: Is the situation truly different with
WLS 6.0? I understand it supports virtual hosting on its own. Can multiple
(web) applications running under a single common WLS "umbrella" server
instance share the same application data? I would expect so - is this true?]

Ruben, I can't help you with the specifics of the configuration but your
general strategy seems correct to me. WLS does not handle multiple certs
and one must front it with a Web server if multiple certs are required.
Neil Smithline
WLS Security Team
BEA Systems
"Ruben-B Reincke" <[email protected]> wrote in message
news:[email protected]...
Hi everybody,
I am trying to figure out a strategy to enable a single web application
based on WLS 4.5.1 (SP13) running on Linux to serve multiple DNS
names, with some specific pages to be transmitted using SSL.
While the JSP pages differ in colouring and screen layout (but not in
logic),
the entire EJB business logic is identical for all DNS names. So are the
servlets.
The application data to be presented to the user can easily be mapped,
and presently (with the application responding to a single DNS name)
it is cached using a JNDI tree. To minimize coding effort, and
to continue utilizing the present caching concept, only expanding it to
support
multiple similar "virtual" applications, I would prefer to
continue using a single WLS instance when making the application"generic".
>
But as a consequence of this, I could only present a single SSLcertificate
to the user if I had WLS answer internet HTTP requests directly.
What would you think should be done to get the browsers
"display the closed padlock while in the order form" for multiple DNSnames
served by this same application instance?
One approach might be to put Apache in front of WLS, and configure it
to serve multiple virtual hosts (one for each DNS name to be served,
encoding the differences between the request URLs somehow in theServerPath
directive, and providing a separate SSL certificate for each of those
virtual
hosts).
Does this make sense to you? Any experience in this area? Which Apache
and WL modules should I be using - which combination
of mod_proxy, mod_ssl (by Apache), mod_wl, mod_wl_ssl[_raven] ?
Any input would be greatly appreciated! Thanks in advance!
Ruben
[A minor add-on question is: Is the situation truly different with
WLS 6.0? I understand it supports virtual hosting on its own. Can multiple
(web) applications running under a single common WLS "umbrella" server
instance share the same application data? I would expect so - is this
true?

HT4864 When trying to update my Mail Account Mailbox Behaviours settings, when I try to close the settings pane the following messages occur: Invalid Incoming Mail Server The "Incoming Mail Server" field cannot be empty. The incoming mail server box has p

When trying to update my Mail Account Mailbox Behaviours settings, after making the changes when I try to close the settings pane the following messages occur: Invalid Incoming Mail Server The “Incoming Mail Server” field cannot be empty. The incoming mail server box has in light grey colour: p02-imap.mail.me.com in it and I cannot edit its content. Any ideas what is going on and how to fix it?

Hi all,
Mattreichenbach is probably on the right track here with a reset of settings. I think I've determined the issue has to do with cached account information and inconsistencies for the account name. This seems to crop up when I've changed my password and it hasn't propagated fully to all the servers, devices, certificates, etc.
Hopefully many here are on their way to restoration of service by now but it's clear that a lot of people are having the same issues. Very frustrating and definitely something Apple needs to resolve: incoming mail server field grayed out, incorrect autopopulation of different fields, other unanticipated behaviors. If you're still having issues, though, here's what worked for me...
First, head to the iCloud preferences pane in System Configuration and choose "Sign Out". When I did this it prompted me with a number of "are you sure" type questions about retaining information on my local machine. I chose to delete/remove the info each time simply because it should all be restored by the cloud and I didn't want to risk a massive duplication of my data... I will say, I'm back up and running with no issues so I suspect you can make the same delete/remove choices... But use your own judgment. I don't want you to lose any data (ie.. please use care as you do this because I cannot bear the thought of causing anyone to experience the pain of data loss).
Once you've signed out of iCloud, restart your system. When you get back in, head to the Mail, Contacts and Calendars section of your System Preferences and add your account back by choosing the brushed aluminum "iCloud" button. When it asks for your account name, use your @iCloud.com email address. I am all but certain my issue had started because one of my devices (iPhone or whatever) had been set up with an email alias specified instead of my @iCloud.com address.
Apple, if you're reading through any of these issues (there are TONS of users having this same problem). Take note, that your icloud service somewhat frequently is not responding and yet tells the user that the password is wrong and this prompts people to be changing their passwords unnecessarily. This has happened to me on numerous occasions. Also, I noticed that last week's outage corresponded to a VERY similar outage exactly one year ago to the day. Sounds like planned maintenance to me and I think you could do a better job notifying folks so we're not wasting HUGE amounts of time troubleshooting a problem that we have no hope of fixing.
Hope that helps some of you!
Terry Mullane
Washington, DC

DNS Name in OD Password Server field?

Similar Messages

Maybe you are looking for