Lacking a FQDN during database mirroring on SQL Server 2005
0
Q:
Lacking a FQDN during database mirroring on SQL Server 2005
I am trying to work with database mirroring on SQL Server 2005, and I keep receiving the error message, “One or more of the server network addresses lacks a fully qualified domain name (FQDN). Specify the FQDN for each server, and click Start Mirroring again.”

I know that the syntax for a fully-qualified TCP address is:
TCP://<computer_name>.<domain_segment>[.<domain_segment>]:<port>

However, I still receive the error. Do you have any ideas?
ASKED: Sep 2 2008  6:59 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
0
46795 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
If SQL is telling you that it can't see the FQDN then either it can't see the internal DNS server, or the SQL Server can not be found in the domains DNS server.

Use the nslookup command line tool to check that DNS is setup correctly for the machine.

nslookup SQLServer.yourdomain.local


Or check with your network admin and have him/her check the DNS server to ensure that the SQL Server has been registered correctly.
Last Answered: Sep 2 2008  9:34 PM GMT by Mrdenny   46795 pts.
0
0
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Mrdenny   46795 pts.  |   Sep 2 2008  9:34PM GMT

Check out my SQL Server blog “SQL Server with Mr Denny” for more SQL Server information.

 
0