Lacking a FQDN during database mirroring on SQL Server 2005

Tags:
Database mirroring
FQDN
SQL Server 2005
SQL Server errors
TCP
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: September 2, 2008  6:59 PM
UPDATED: October 22, 2013  4:59 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

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.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following