Networking set up on workstation not quite right, yet

Latest response

I've installed a fresh copy of RHEL Workstation (moved over from FC, glad I did).  I'm experiencing some network domain issues.  I can get to the network (local and outside), but my domain name stuff is not quite right.

Details:

  • IP address is set/retrieved via DHCP
  • ifconfig returns:

$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:13:72:2F:1B:3D 
          inet addr:192.168.43.105  Bcast:192.168.43.255  Mask:255.255.255.0

  • contents of /etc/resolve.conf:

# Generated by NetworkManager
domain office.mydomain.com
search office.mydomain.com
nameserver 192.168.43.61

  • contents of /etc/hosts:

127.0.0.1   localhost rhineheart.office.mydomain.com rhineheart
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

  • domainname, hostname, hostname -i, hostname -f output:

[me@rhineheart ~]$ domainname
(none)
[me@rhineheart ~]$ hostname
rhineheart.office.mydomain.com
[me@rhineheart ~]$ hostname -i
127.0.0.1
[me@rhineheart ~]$ hostname -f
localhost

  • Contents of /etc/sysconfig/network:

NETWORKING=yes
HOSTNAME=rhineheart.office.mydomain.com
 

  • nslookup rhineheart:

Server:        192.168.43.61
Address:    192.168.43.61#53

** server can't find rhineheart: SERVFAIL
 

  • /etc/nsswitch.conf:

hosts:      dns files

ethers:     files
netmasks:   files
networks:   files
 

Our main domain (mydomain.com) is hosted on another network.  The domain 'office.mydomain.com' is our local office.

Hmmm. Ideas?
 

th
Log in to join the conversation

Responses

RJ Active Contributor 212 points
24 July 2013 8:24 PM

It looks like DNS lookups are broken, and I think I may see why.  You listed good-looking contents of "/etc/resolve.conf" but that stuff should be in "/etc/resolv.conf" (with no second "e").  Was that a typo in your post or on the machine?

th Community Member 40 points
24 July 2013 8:32 PM

Whoops, definitely typo.  File name is '/etc/resolv.conf'.

Also, 'dnsdomainname' returns no output.....

james.radtke@siriusxm.com's picture Guru 6863 points
24 July 2013 8:39 PM

Is your DHCP server (and DNS server) DynDNS capable?  You need to have the client report to your DNS environment that your workstation has joined the network.

I think..  you may want to add this to /etc/sysconfig/network-scripts/ifcfg-eth0

DHCP_HOSTNAME=rhineheart.office.mydomain.com

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-dhcp-configuring-client.html

DDNS can get reasonably complicated, but it's certainly not impossible ;-)  I believe the DHCP server needs "allow-updates" configured and there is a key that needs to be created and integrated with the name server.

RJ Active Contributor 212 points
24 July 2013 8:42 PM

The "SERVFAIL" concerns me.  What does a "nslookup rhineheart.office.mydomain.com" return?

Remove the "rhineheart.office.mydomain.com rhineheart" from the end of the "localhost" line in /etc/hosts and see if that helps.

th Community Member 40 points
24 July 2013 8:49 PM

I'll look into those two items.

thanks.

th Community Member 40 points
24 July 2013 8:53 PM

$ nslookup rhineheart.office.mydomain.com
Server:        192.168.43.61
Address:    192.168.43.61#53

** server can't find rhineheart.office.mydomain.com: NXDOMAIN
 

james.radtke@siriusxm.com's picture Guru 6863 points
24 July 2013 8:56 PM

and .. to be forthcoming .. mine does not always seem to update our AD DNS.  ;-)

I think I understand what you are trying to do, but I'll repeat just to be sure:

You would like to reboot your workstation, and have the hostname that you have given it report back to your Network's DNS servers.  So - that way you can get back to your own workstation from other machines, or when you connect to a server, it knows the hostname of where you connected from.  Does that sound like we're on the same page?

From my own experience, my windows workstation ALWAYS works this, my Mac workstation usually works and my RHEL 6 workstation works about 10% of the time.  I have no idea sometimes it seems to work and others it does not, but I have not had a reason to look into it.

Please let us know if the suggestions worked for you.

james.radtke@siriusxm.com's picture Guru 6863 points
24 July 2013 9:15 PM

and .. to be forthcoming .. mine does not always seem to update our AD DNS.  ;-)

I think I understand what you are trying to do, but I'll repeat just to be sure:

You would like to reboot your workstation, and have the hostname that you have given it report back to your Network's DNS servers.  So - that way you can get back to your own workstation from other machines, or when you connect to a server, it knows the hostname of where you connected from.  Does that sound like we're on the same page?

From my own experience, my windows workstation ALWAYS works this, my Mac workstation usually works and my RHEL 6 workstation works about 10% of the time.  I have no idea sometimes it seems to work and others it does not, but I have not had a reason to look into it.

Please let us know if the suggestions worked for you.

th Community Member 40 points
24 July 2013 9:44 PM

Yes, that's correct.  I'll work on the suggestions tomorrow.  Our DNS/DHCP server is a Windows Server box.  that'll be fun to work with....

CH Community Member 52 points
30 July 2013 8:35 PM

I've had limited success in getting AD DNS to update from my Redhat clients. The easiest solution is to reserve the IP address in DHCP and add static DNS entries.

You can try

DHCP_HOSTNAME=

in your /etc/sysconfig/network-scripts/ifcfg-eth* file.

 

Check the AD security/app logs and see if it's getting an error from your workstation. Thats where you will need to look next.

 

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.