# Could not resolve the DNS issue

**URL:** <https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477>\
**Category:** SLES Networking\
**Created:** [October 18, 2019, 9:46pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477 "2019-10-18T21:46:51Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![csreddym](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@csreddym](https://forums.suse.com/u/csreddym)\
**Post date:** [October 18, 2019, 9:46pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/1 "2019-10-18T21:46:51Z")

</div>

Hi Experts,

I am new to SUSE LInux and I am trying to install SAP system.  
I am facing the below issue while starting installation.

# Problem with the DNS configuration: could not determine the DNS domain of host localhost

Below are config details: If i do nslookup to local host it is resolving.

localhost:~ # nslookup localhost  
Server: 62.241.198.246  
Address: 62.241.198.246#53

# Non-authoritative answer: Name: localhost Address: 127.0.0.1

Under network settings, hostname is mentioned localhost and domain mentioned as suse by default.  
iN this case it is not resolving.

localhost:~/saptemp # nslookup localhost.suse

Server: 62.241.198.246

Address: 62.241.198.246#53

\*\*  
server can’t find localhost.suse: NXDOMAIN

======================================  
more /etc/resolv.conf

### /etc/resolv.conf

search [pp.htv.fi](http://pp.htv.fi)

nameserver 62.241.198.246

nameserver 62.241.198.245

What could be the issue in this case?  
I am not linux admin, if some can help on this would be great.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [October 19, 2019, 12:30am UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/2 "2019-10-19T00:30:14Z")

</div>

Hi  
You should be using a FQDN (Fully Qualified Domain Name) the .suse is just for local use and temporarily until you set your hostname and domain. This is normally done via YaST network settings against the interface(s) in use.

I normally set mine also in the /etc/hosts file against 127.0.0.2

For example;

```auto
hostname -f

oscar.homelinux.org

dig oscar.homelinux.org @gekkota-dns1

; <<>> DiG 9.11.2 <<>> oscar.homelinux.org @gekkota-dns1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7080
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;oscar.homelinux.org. IN	A

;; ANSWER SECTION:
oscar.homelinux.org.	2	IN	A	192.168.10.80

;; Query time: 5 msec
;; SERVER: 192.168.10.3#53(192.168.10.3)
;; WHEN: Fri Oct 18 16:25:20 CDT 2019
;; MSG SIZE rcvd: 64
```

---

<div class="post-metadata">

**Author:** ![csreddym](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@csreddym](https://forums.suse.com/u/csreddym)\
**Post date:** [October 19, 2019, 5:21pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/3 "2019-10-19T17:21:02Z")

</div>

Hi Malcolmlewis,

Thanks for your response.  
Below is current status. Still i am unable to resolve DNS by giving this way: nslookup sapecc  
Something I am missing which i am unable to trace it out.  
Seeking more help on this.

apecc:/etc # dig [sapecc.chandra.com](http://sapecc.chandra.com)

; \<\<\>\> DiG 9.9.6-P1 \<\<\>\> [sapecc.chandra.com](http://sapecc.chandra.com)

;; global options: +cmd

;; Got answer:

;; -\>\>HEADER\<\<- opcode: QUERY, status: NOERROR, id: 25110

;; flags: qr rd ra  
; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:  
; udp: 4096

;; QUESTION SECTION:

;[sapecc.chandra.com](http://sapecc.chandra.com). IN A

;; ANSWER SECTION:  
[sapecc.chandra.com](http://sapecc.chandra.com). 300 IN A 64.99.80.121

;; Query time: 272 msec

;; SERVER: 62.241.198.246#53(62.241.198.246)

;; WHEN: Sat Oct 19 10:14:24 EDT 2019

;; MSG SIZE rcvd: 63

==========================

sapecc:/etc # nslookup [sapecc.chandra.com](http://sapecc.chandra.com)

Server: 62.241.198.246

Address: 62.241.198.246  
#53

Non-authoritative answer:

Name: [sapecc.chandra.com](http://sapecc.chandra.com)

Address: 64.99.80.121

============================

Host file:

# IP-Address Full-Qualified-Hostname Short-Hostname

# 

127.0.0.1 [sapecc.chandra.com](http://sapecc.chandra.com) sapecc  
#127.0.0.1 localhost

# special IPv6 addresses

::1 localhost ipv6-localhost ipv6-loopback

fe00::0 ipv6-localnet

ff00::0 ipv6-mcastprefix

ff02::1 ipv6-allnodes

ff02::2 ipv6-allrouters

ff02::3 ipv6-allhosts

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [October 19, 2019, 7:12pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/4 "2019-10-19T19:12:25Z")

</div>

Hi  
The 127.0.0.1 and localhost are important, move your hostname and fqdn to 127.0.0.2 instead.

It all resolves here, so it must be your DNS servers that are the issue…

```auto
nslookup sapecc.chandra.com

Server: 192.168.10.3
Address:	192.168.10.3#53

Non-authoritative answer:
Name:	sapecc.chandra.com
Address: 64.99.80.121

dig sapecc.chandra.com @8.8.8.8

; <<>> DiG 9.11.2 <<>> sapecc.chandra.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43799
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;sapecc.chandra.com. IN	A

;; ANSWER SECTION:
sapecc.chandra.com.	299	IN	A	64.99.80.121

;; Query time: 114 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Oct 19 11:10:16 CDT 2019
;; MSG SIZE rcvd: 63
```

---

<div class="post-metadata">

**Author:** ![strahil-nikolov-dxc](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@strahil-nikolov-dxc](https://forums.suse.com/u/strahil-nikolov-dxc)\
**Post date:** [October 19, 2019, 8:00pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/5 "2019-10-19T20:00:00Z")

</div>

By the way, SLES11 is in last phase of support (even for SAP-based one) and it is highly recommended to switch either to SLES12SP4 or even ro SLES15SP1.

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [October 19, 2019, 8:17pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/6 "2019-10-19T20:17:18Z")

</div>

> [@strahil-nikolov-dxc;58692](#):
>
> By the way, SLES11 is in last phase of support (even for SAP-based one) and it is highly recommended to switch either to SLES12SP4 or even ro SLES15SP1.

Hi  
LTSS goes to 31 Mar 2022 for SUSE Linux Enterprise Server for SAP Applications 11 SP4. It’s already out of general support…

---

<div class="post-metadata">

**Author:** ![csreddym](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@csreddym](https://forums.suse.com/u/csreddym)\
**Post date:** [October 21, 2019, 11:38am UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/7 "2019-10-21T11:38:20Z")

</div>

Hi Malcolm,

Thanks for your help and pointed to help on the issue in the right direction.  
Finally I am able to solve with your help.  
It is the problem in DNS setting where currently it was to Auto mode to obtain IP automatically.  
This was the issue which was causing this. I have changed to static by assigning IP.  
Thanks for your help once again:)

---

<div class="post-metadata">

**Author:** ![sai\_arvindh](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/sai_arvindh/32/11485_2.png) [@sai\_arvindh](https://forums.suse.com/u/sai_arvindh)\
**Post date:** [August 24, 2024, 12:32pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/8 "2024-08-24T12:32:30Z")

</div>

Hi brother,

I face the same issue while installing SAP. Can you please help me with the below concern.

1. which Hostname do I need to put in Hostfile
2. which IP address do I need to put it hostfile
3. which static IP i need to set in RESOLV.CONF

Please help me with the above concern. I dont have any backround of Linux related stuff.

Thanks

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [August 24, 2024, 1:10pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/9 "2024-08-24T13:10:58Z")

</div>

@sai_arvindh You should be able to configure all via YaST Networking?

---

<div class="post-metadata">

**Author:** ![sai\_arvindh](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/sai_arvindh/32/11485_2.png) [@sai\_arvindh](https://forums.suse.com/u/sai_arvindh)\
**Post date:** [August 24, 2024, 1:25pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/10 "2024-08-24T13:25:25Z")

</div>

Hello brother,

Config I can do directly on Windows settings (DNS) and the hostfile from the respective path.

My concern is all about which IP and Hostname do I need to configure to bypass the error while I install SAP.

If you can help me on that please.

Thanks

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [August 24, 2024, 1:56pm UTC](https://forums.suse.com/t/could-not-resolve-the-dns-issue/34477/11 "2024-08-24T13:56:44Z")

</div>

@sai_arvindh what ever has been allocated on your network for the system? Is this a virtual machine, bare-metal?