cancel
Showing results for 
Search instead for 
Did you mean: 

Netweaver 7.51 installation: Error Unable to determine parameter "DNS domain name".

Former Member
0 Kudos

Hello,

I am installing SAP Netweaver AS 7.51 on my (K)Ubuntu machine using Oracle VirtualBox and yet another (K)Ubuntu instance. I have followed this guide which I find tremendously helpful to the letter.

I have assigned 100GB of space and 6GB of RAM, 2 processors on a 64-bit system. VirtualBox is in a bridged networking mode, so the guest system is visible on my network as separate device.

So far so good, however, during installation I get the following error message while the installation process aborts:

Unable to determine parameter "DNS domain name". DNS domain name is not configured in resolv.conf (UNIX) or the registry (Windows) and neither getaddrinfo nor gethostbyname could retrieve it.
Failed action:  with parameters 
Error number 301 error type SPECIFIC_CODE

/etc/hosts:

127.0.0.1       localhost
192.168.168.150 vhcalnplci vhcalnplci.dummy.nodomain

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

/etc/resolv.conf:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 192.168.168.230
nameserver 127.0.0.53

If anyone can point me in the right direction I would be very grateful. I am a Linux enthusiast and not easily scared away, so please keep your questions coming.

Thank you / wieman01

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

I had the same problem with two machines, a Windows10-PC with an openSUSE-VM and a Windows10-Laptop with a Linux Mint 18.2-VM. The openSUSE was in NAT-mode (with nameserver 192.168.200.1 - my router - in /etc/resolv.conf), the Mint-VM was in bridged mode (with nameserver 127.0.1.1 in /etc/resolv.conf).

I then changed the setting of the Linux Mint-VM to NAT, also. I wanted to check if the entry in /etc/resolv.conf gets altered automatically. I found that it stayed at 127.0.1.1. Now my installation of SAP 7.50 was suddenly successfull!


The weird thing is that I expected to see the same result when chaning the first VM. It was already set to NAT but /etc/resolv.conf showed my local router's IP. So I changed it to 127.0.1.1. But with this setting I don't have any access any more to the local or internet network.

What worked with Linux Mint 18.2 did not work with openSUSE but I don't know why.

Former Member
0 Kudos

Hello,

I was finally able to resolve this issue by doing the following:

  • I install Ubuntu Server 18.04 without a graphical interface and configured it to use a static IP address.
  • I also installed the package 'resolvconf' to add my gateway as a DNS.
  • Finally I changed my router settings and gave the device a new hostname: dummy.nodomain.

The DNS issue during the installation process has disappeared and is no longer a problem. Here are a few code samples to guide you through the solutions.

Open a terminal:

sudo nano /etc/netplan/01-netcfg.yaml

Then add (make sure 'enp0s3' is replaced with your network adapter; also add your gateway's and client's IP address):

# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
    enp0s3:
     dhcp4: no
     addresses: [192.168.1.150/24]
     gateway4: 192.168.1.200
     nameservers:
       addresses: [192.168.1.200]

Install & configure package 'resolvconf' (add your gateway's IP address):

sudo apt-get install resolvconf
echo nameserver 192.168.1.200 >> /etc/resolvconf/resolv.conf.d/head
resolvconf --enable-updates
resolvconf -u

Apply network settings:

sudo netplan apply
or
sudo reboot now

This is it. Test if everything is working by pinging your domain as well as your hostname (see post #2).

Former Member
0 Kudos

Just in case this piece of information is helpful and anyone is wondering:

ping vhcalnplci

...returns my guest's IP address.

ping vhcalnplci.dummy.nodomain

...returns my guest's IP address.

ping dummy.nodomain

...returns my gateway's IP address.

I have assigned a static IP address and have disabled DHCP.