Definately not a linux expert and having some network setup issues. I'm configuring through YAST - but it's not updating DNS information in the resolv.conf file.

YAST settings
Hostname=linux-m8ni DNS=tristan-dom

When I execute a nslookup, this is what I get
nslookup linux-m8ni.tristan-dom
Server: 8.8.8.8
Address: 8.8.8.8#53

** server can't find linux-m8ni.tristan-dom: NXDOMAIN

My resolv.conf looks like this
search tristan-dom hsd1.tx.comcast.net
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 2001:558:feed::2

I'm trying to install an SAP server here at my house and I think this is the thing causing me all of my issues. I can't resolve the FQDN. Any thoughts?

Maybe I'm behind the times, but that doesn't look like a FQDN to me...

Shouldn't it be linux-m8ni.tristan.com or some other top-level domain?

You can pretty much make up your own rules when it comes to private IP space and a single host. The OP's intent should work, providing that the /etc/hosts file has the right info.

Name resolution is a combination of different files and services - it isn't all done with the /etc/resolv.conf file.

By default, openSUSE will set your machine to use files first, then switch over to DNS if those don't work (see the /etc/nsswitch.conf file, look for the "hosts" entry - you will see "files dns").

The "files" reference is for the /etc/hosts file primarily. Check that file to see if there is an entry for your FQDN (linux-m8ni.tristan-dom). More often than not, only the hostname portion (linux-m8ni) will be present referencing your configured IP Address. You can edit this file and add "linux-m8ni.tristan-dom" after the "linux-m8ni" entry (put a blank space between then) so that you can access the machine by hostname -OR- FQDN.

The issue you will run into next is other machines on your network being able to reach that machine via FQDN. You'll need to update the hosts files on Windows machines with the same entry as what you'll end up with on your Linux machine, or you'll have to run your own DNS server on your LAN and add an entry.

Thanks for the insight. Domain name was a typo in the network settings through YAST - unfortunately it won't change now as it gets reset after saving each time. I'm kindof at the same space though - what's the harm.

You are correct with the nsswitch.conf
hosts: files dns

Host file
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
10.10.10.10 linux-m8ni.tristan-dom linux-m8ni


Is there an issue with the fact that the FQDN is before the linux-m8ni??

I'm not sure where this gets me with my orginal question - and ultimate issue with not being able to install SAP. I still think there is some sort of issue with resolving to linux-m8ni.tristan-dom (as I think I'm seeing with the nslookup).

Unfortunately, I've spent 20 years with SAP and 20 hours with linux and really don't know what I'm doing here :-(

Name resolution starts with "files" then moves on to "DNS" if there's no info available in the files. By trying to resolve with nslookup, you are skipping the files portion and forcing DNS. Try just "ping linux-m8ni.tristan-dom" from the CLI and see if it comes back with your IP correctly.

Is this machine getting its IP Address via DHCP? If so, much of this is moot as the DHCP server controls a -lot- of that information unless you check the boxes in the network setup to prevent DHCP from overwriting values you specify.