Source:How to check DNS configuration: Difference between revisions

From SEPsesam
(Marked this version for translation)
(31 intermediate revisions by 6 users not shown)
Line 1: Line 1:
= How to check DNS configuration =
<noinclude><div class="noprint"><languages />
<br />


== General ==
<translate>== Overview == <!--T:2--> </translate>


Most of our customers face problems while configuring new clients. Often the source of the problems are misconfigured
{{Additional_Resources_Box|seeAlsoLinks=<nowiki />
DNS Servers, or no functional DNS at all. This document describes how to use Sesam with DNS names and how to check
*<translate><!--T:5-->
wether if your DNS configuration is OK.
[[Special:MyLanguage/FAQ#name_resolution|Why do I get the message: "Login incorrect. Password incorrect." during the backup?]]
*[[Special:MyLanguage/FAQ#profile_setting|What happens when I set a profile?]]</translate>}}


== Requirements and Rules ==
</div></noinclude><translate><!--T:8-->
Certain problems can occur when configuring new clients in SEP sesam if the DNS server is incorrectly configured or missing. SEP sesam needs a correct DNS to work and will not work with just an IP address. All DNS names must be correctly resolved (forward and reverse DNS lookup).


* Sesam needs a propper DNS to work, it will NOT work with IP Adresses
<!--T:9-->
* All DNS Names have to correctly resolve forward and reverse
If the DNS server is missing, you will have to use the '''hosts file''' of the client and backup server to make systems available via a DNS name. The hosts file can be found in the following locations:</translate>
* If no DNS Server is available, the hosts file of the client and backup server have to be used for making systems available via DNS name
* The Hostname of the Sesam server is not allowed to include a underscore "_" sign (see: wikipedia: [http://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names])


== Configuration ==
;Linux
/etc/hosts
 
;Windows
C:\Windows\system32\drivers\etc\hosts
 
{{note|<translate><!--T:10--> The hostname of the SEP sesam server may not include an underscore "_" sign. For hostname restrictions, see [http://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names Restrictions on valid host names].</translate>}}
 
== {{anchor|tools}}<translate><!--T:11--> Tools for checking DNS resolution </translate> ==
 
<translate><!--T:12-->
Several tools are available to check DNS resolution. However, SEP recommends the use of <tt>sm_setup check_resolution</tt>.</translate>
 
=== {{anchor|sm_setup_check}}<translate><!--T:13--> <tt>sm_setup check_resolution</tt> (recommended)</translate> ===


=== Common Error Messages ===
<translate><!--T:14-->
The SEP sesam <tt>sm_setup</tt> tool is part of the SEP sesam Client and Server installation and can be used from the command line to resolve DNS names. Before using this tool, you need to set up a SEP sesam profile as described in FAQ: [[Special:MyLanguage/FAQ#profile_setting|What happens when I set up a profile?]]


There are some common error messages which are an indication for errors in your name resolution:
<!--T:15-->
SEP recommends that you run this command on the backup server AND on the client with the same arguments. It is important that the client and the backup server are resolved correctly.
 
<!--T:16-->
;Syntax</translate>
'''Client''':~ # sm_setup check_resolution '''backupserver'''
Calling getaddrinfo with ''''backupserver''''
        Official name: '''backupserver.sep.de'''
        IPv4 Address #1: '''172.16.1.146'''
Calling getnameinfo for IP Address #1 ''''172.16.1.146''''
        Official name: '''backupserver.sep.de'''
        Alternate name: backupserver


  CLIENT_HOSTNAME: Login to stpd from <CLIENT_HOSTNAME> to <SESAM_SERVER_HOSTNAME> incorrect.
  '''Client''':~ # sm_setup check_resolution '''client'''
Calling getaddrinfo with ''''client''''
        Official name: '''client.sep.de'''
        IPv4 Address #1: '''172.16.1.145'''
Calling getnameinfo for IP Address #1 ''''172.16.1.145''''
        Official name: '''client.sep.de'''
        Alternate name: client
<br>
'''Backupserver''':~ # sm_setup check_resolution '''client'''
' Calling getaddrinfo with ''''client''''
        Official name: '''client.sep.de'''
        IPv4 Address #1: '''172.16.1.145'''
Calling getnameinfo for IP Address #1 ''''172.16.1.145''''
        Official name: '''client.sep.de'''
        Alternate name: client
 
'''Backupserver''':~ # sm_setup check_resolution '''backupserver'''
Calling getaddrinfo with ''''backupserver''''
        Official name: '''backupserver.sep.de'''
        IPv4 Address #1: '''172.16.1.146'''
Calling getnameinfo for IP Address #1 ''''172.16.1.146''''
        Official name: '''backupserver.sep.de'''
        Alternate name: backupserver
 
 
<translate><!--T:17-->
The returned addresses and hostnames must match. If the reverse resolve returns an ''official name'' that is different from the name specified on the command line, problems will occur when backing up the client (see [[#messages|Common error messages]]).</translate>


Login incorrect. Client resolves his IP address [X.X.X.X] to [RANDOM_HOSTNAME], but server resolves it to [X.X.X.X]. Please adjust your name resolution.  (0)
==={{anchor|nslookup}}<translate><!--T:18--> <tt>nslookup</tt> (Windows and Linux)</translate>===


=== Hosts Files ===
<translate><!--T:19-->
The <tt>nslookup</tt> tool is a network administration command-line tool for querying the DNS to obtain a hostname or IP address.


==== Linux ====
<!--T:20-->
It is useful for troubleshooting DNS issues, but not for full hostname resolution as it ignores the hosts file. SEP sesam resolves its hostnames via the "common library function" and first uses the hostname specified in the hosts file of the system. By default, nslookup translates a domain name to an IP address (or vice versa).


If an hosts file has to be used because of no DNS servers in your network, the file on the system is placed
<!--T:21-->
in:
Use the <tt>nslookup</tt> command to check that the name resolution is correct: ''forward'' with and without FQDN as well as ''reverse''. Check on the SEP sesam Server AND on the SEP sesam Client. If DNS is not used and the verification done via the <code>etc/hosts</code> file, use [[#ping|ping]] to check individual clients.


/etc/hosts
<!--T:22-->
;Syntax</translate>
        nslookup {client}
        nslookup {IP-Address of client}                        # important reverse lookup
        nslookup {SEPsesam Server name}
        nslookup {IP-Address of SEPsesam Server}                # important reverse lookup


==== Windows ====
<translate><!--T:23-->
Example: check ''mysesam'' name resolution and reverse lookup:</translate>


If you want to use a hosts file on windows Systems for working around DNS problems, the
      #>nslookup mysesam
file can be found in:
      Server:   dns.domaine.de
      Address:  192.168.1.254


  C:\Windows\system32\drivers\etc\hosts
      Name:    mysesam.domaine.de
      Address: 192.168.1.1


=== Tools to check DNS Resolution ===
      #>nslookup 192.168.1.1
      Server:  dns.domaine.de
      Address:  192.168.1.254


There are various tools which can be used to check the DNS resolution, they have up and downsides.
      Name:    mysesam.domaine.de
The recommended way to check your dns configuration is to use [[How_to_check_DNS_configuration#sm_setup_check_resolution_.28recommended.29]]
      Address:  192.168.1.1


==== ping ====
=== {{anchor|host}}<translate><!--T:24--> <tt>host</tt> (Linux only)</translate>===


ping is not a proper tool to check DNS resolution, it will not allways be 100% correct. It is
<translate><!--T:25-->
also not possible to correctly reverse resolve the DNS names.
The <tt>host</tt> command can also be used to resolve a hostname into an IP address and vice versa. It defaults to the name server configured in <code>/etc/resolv.conf</code> but can also be used with a DNS server as an additional argument. It will query the DNS server of the system first.


==== nslookup (windows and linux) ====
<!--T:26-->
;Syntax</translate>
'''Client''':~ # host '''backupserver'''
                      backupserver.sep.de has address '''172.16.1.146'''


This tool can be used to query and existing DNS Server for a certain hostname or ip address. It
'''Client''':~ # host '''172.16.1.146'''
will NOT check the hosts file of the System. As such, you may get different results if you choose
                      146.1.16.172.in-addr.arpa domain name pointer '''backupserver.sep.de'''
to use nslookup. Sesam resolves its hostnames via common library function and will first use
the hostname specified in the hostsfile of the system.


==== host (linux only) ====
==={{anchor|ping}}<translate><!--T:27--> <tt>ping</tt></translate>===


As nslookup, host can be used to forward and reverse resolve hostnames and ip adresses. It
<translate><!--T:28-->
defaults to the DNS server configured in /etc/resolv.conf but can also be used wit a certain
<tt>ping</tt> is a network administration software utility used to test the reachability of a destination device on an IP network via ICMP echo request. It is not a suitable tool for checking DNS resolution and will not always be 100% correct. Although ping resolves an IP address, it is not strictly a name server lookup tool and may return a potentially outdated cached result.  
DNS Server as additional argument. It will query the DNS Server of the System first.


==== sm_setup check_resolution (recommended) ====
<!--T:29-->
In addition, it is not possible to correctly reverse resolve DNS names. For more details, see the [https://en.wikipedia.org/wiki/Ping_%28networking_utility%29 ping description on Wikipedia].</translate>


This is the recommended way to check your DNS Resolution. Both client and backup servers
=={{anchor|messages}}<translate><!--T:30--> Common error messages</translate>==
come with the sesam tool "sm_setup" installed. It can be used to forward and reverse resolve
DNS names from the Command Line.


Before you can use this tool, be sure to execute the Sesam Profile like shown in this
<translate><!--T:31-->
FAQ entry:
The following common error messages indicate that there is a problem with your name resolution:</translate>


[[English_FAQ#A_support_staff_member_told_me_to_set_a_profile.2C_what_does_he_mean.3F]]
CLIENT_HOSTNAME: Login to stpd from <CLIENT_HOSTNAME> to <SESAM_SERVER_HOSTNAME> incorrect.


It is recommended to run this command on the backup server AND on the client with different
Login incorrect. Client resolves his IP address [X.X.X.X] to [RANDOM_HOSTNAME], but server resolves it to [X.X.X.X]. Please adjust your name resolution. (0)
arguments. On the backup server, the second argument will be the desired hostname of the
client. If executing the command at the client, the second argument will be the hostname
of the backup server.


The output of the command looks like this:
<translate><!--T:32-->
In this case, check your name resolution (DNS or <tt>etc/hosts</tt> file). The SEP sesam Server and the SEP sesam Client must be reachable with or without FQDN and should be able to resolve each other and also themselves correctly, including reverse lookup.


backup_server:~ # sm_setup check_resolution '''client'''
<!--T:33-->
Calling gethostbyname with ' '''client''' '
If you have changed an entry in your DNS configuration, but Windows still reports a wrong hostname/IP, try running <tt>ipconfig /flushdns</tt> as administrator.</translate>
        Official name: '''client.sep.de'''
        Address type: AF_INET
        Address length: 4
        First IP Address: '''172.16.1.145'''
Calling gethostbyaddr with ''''172.16.1.145''''
        Official name: '''client.sep.de'''
        Address type: AF_INET
        Address length: 4
        First IP Address: '''172.16.1.145'''


As you can see the command will output the forward and reverse resolved hostname
<div class="noprint"><noinclude>
of the system. Both the addresses and hostnames which are returned have to
==<translate><!--T:34-->
match. For example if the Official name which is returned from the reverse
See also==
resolve is different from the on specified on the command line, this will
[[Special:MyLanguage/FAQ#name_resolution|Why do I receive the message: "Login incorrect. Password incorrect." during backup?]] – [[Special:MyLanguage/FAQ#profile_setting|What happens when I set a profile?]]</translate>
result in problems backing up the client (see [Common Error Messages])
The same values have to match on the client for the hostname of the backup
server:


client:~ # sm_setup check_resolution backup_server
{{Copyright}}</noinclude></div>
Calling gethostbyname with 'backup_server'
        Official name: backup_server.sep.de
        Address type: AF_INET
        Address length: 4
        First IP Address: 172.16.1.146
Calling gethostbyaddr with '172.16.1.146'
        Official name: backup_server.sep.de
        Address type: AF_INET
        Address length: 4
        First IP Address: 172.16.1.146

Revision as of 10:56, 18 September 2023


Overview


Certain problems can occur when configuring new clients in SEP sesam if the DNS server is incorrectly configured or missing. SEP sesam needs a correct DNS to work and will not work with just an IP address. All DNS names must be correctly resolved (forward and reverse DNS lookup).

If the DNS server is missing, you will have to use the hosts file of the client and backup server to make systems available via a DNS name. The hosts file can be found in the following locations:

Linux
/etc/hosts
Windows
C:\Windows\system32\drivers\etc\hosts
Note
The hostname of the SEP sesam server may not include an underscore "_" sign. For hostname restrictions, see Restrictions on valid host names.

Tools for checking DNS resolution

Several tools are available to check DNS resolution. However, SEP recommends the use of sm_setup check_resolution.

sm_setup check_resolution (recommended)

The SEP sesam sm_setup tool is part of the SEP sesam Client and Server installation and can be used from the command line to resolve DNS names. Before using this tool, you need to set up a SEP sesam profile as described in FAQ: What happens when I set up a profile?

SEP recommends that you run this command on the backup server AND on the client with the same arguments. It is important that the client and the backup server are resolved correctly.

Syntax
Client:~ # sm_setup check_resolution backupserver
Calling getaddrinfo with 'backupserver'

        Official name: backupserver.sep.de
        IPv4 Address #1: 172.16.1.146

Calling getnameinfo for IP Address #1 '172.16.1.146'

        Official name: backupserver.sep.de
        Alternate name: backupserver
Client:~ # sm_setup check_resolution client
Calling getaddrinfo with 'client'

        Official name: client.sep.de
        IPv4 Address #1: 172.16.1.145

Calling getnameinfo for IP Address #1 '172.16.1.145'

        Official name: client.sep.de
        Alternate name: client


Backupserver:~ # sm_setup check_resolution client
' Calling getaddrinfo with 'client'

        Official name: client.sep.de
        IPv4 Address #1: 172.16.1.145

Calling getnameinfo for IP Address #1 '172.16.1.145'

        Official name: client.sep.de
        Alternate name: client

Backupserver:~ # sm_setup check_resolution backupserver
Calling getaddrinfo with 'backupserver'

        Official name: backupserver.sep.de
        IPv4 Address #1: 172.16.1.146

Calling getnameinfo for IP Address #1 '172.16.1.146'

        Official name: backupserver.sep.de
        Alternate name: backupserver


The returned addresses and hostnames must match. If the reverse resolve returns an official name that is different from the name specified on the command line, problems will occur when backing up the client (see Common error messages).

nslookup (Windows and Linux)

The nslookup tool is a network administration command-line tool for querying the DNS to obtain a hostname or IP address.

It is useful for troubleshooting DNS issues, but not for full hostname resolution as it ignores the hosts file. SEP sesam resolves its hostnames via the "common library function" and first uses the hostname specified in the hosts file of the system. By default, nslookup translates a domain name to an IP address (or vice versa).

Use the nslookup command to check that the name resolution is correct: forward with and without FQDN as well as reverse. Check on the SEP sesam Server AND on the SEP sesam Client. If DNS is not used and the verification done via the etc/hosts file, use ping to check individual clients.

Syntax
       nslookup {client}
       nslookup {IP-Address of client}                         # important reverse lookup
       nslookup {SEPsesam Server name}
       nslookup {IP-Address of SEPsesam Server}                # important reverse lookup

Example: check mysesam name resolution and reverse lookup:

     #>nslookup mysesam
     Server:   dns.domaine.de
     Address:  192.168.1.254
     Name:     mysesam.domaine.de
     Address:  192.168.1.1
     #>nslookup 192.168.1.1
     Server:   dns.domaine.de
     Address:  192.168.1.254
     Name:     mysesam.domaine.de
     Address:  192.168.1.1

host (Linux only)

The host command can also be used to resolve a hostname into an IP address and vice versa. It defaults to the name server configured in /etc/resolv.conf but can also be used with a DNS server as an additional argument. It will query the DNS server of the system first.

Syntax
Client:~ # host backupserver
                     backupserver.sep.de has address 172.16.1.146

Client:~ # host 172.16.1.146
                     146.1.16.172.in-addr.arpa domain name pointer backupserver.sep.de

ping

ping is a network administration software utility used to test the reachability of a destination device on an IP network via ICMP echo request. It is not a suitable tool for checking DNS resolution and will not always be 100% correct. Although ping resolves an IP address, it is not strictly a name server lookup tool and may return a potentially outdated cached result.

In addition, it is not possible to correctly reverse resolve DNS names. For more details, see the ping description on Wikipedia.

Common error messages

The following common error messages indicate that there is a problem with your name resolution:

CLIENT_HOSTNAME: Login to stpd from <CLIENT_HOSTNAME> to <SESAM_SERVER_HOSTNAME> incorrect.
Login incorrect. Client resolves his IP address [X.X.X.X] to [RANDOM_HOSTNAME], but server resolves it to [X.X.X.X]. Please adjust your name resolution.  (0)

In this case, check your name resolution (DNS or etc/hosts file). The SEP sesam Server and the SEP sesam Client must be reachable with or without FQDN and should be able to resolve each other and also themselves correctly, including reverse lookup.

If you have changed an entry in your DNS configuration, but Windows still reports a wrong hostname/IP, try running ipconfig /flushdns as administrator.

See also

Why do I receive the message: "Login incorrect. Password incorrect." during backup?What happens when I set a profile?

Copyright © SEP GmbH (formerly SEP AG) 1999-2025. All rights reserved.
Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP GmbH. When compiling and designing user documentation SEP GmbH uses great diligence and attempts to deliver accurate and correct information. However, SEP GmbH cannot issue a guarantee for the contents of this manual.