Sponsored Content
Full Discussion: Loghost as DNS alias
Special Forums UNIX and Linux Applications Loghost as DNS alias Post 302435280 by mohzub on Wednesday 7th of July 2010 03:17:38 AM
Old 07-07-2010
Loghost as DNS alias

We have about 5000 unix servers and currently loghost is listed in the /etc/host on all of the 5000 servers. Since the loghost server is not using SAN storage, the server was never implemented in GeoVLAN either.

We are going to implement DR instance for loghost with local storage ( as advise by our global) and in non-GeoVLAN farm.

With the current setup, it will be an issue if we are to activate the DR. This is because it will mean updating all the 5000 servers with the DR IP address and that is not a good idea.

The other option is to create loghost as DNS alias and remove loghost from /etc/host file in all the unix servers.

Do anyone see issue on performance or anything like that if we are to go with DNS alias?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Loghost

I need to configure a LOGHOST. have several machines reporting to it (SOL 2.6 to 2.8) for each host that reports to the LOGHOST I need a spearte directory/and log, instead of of big log. Any ideas? (1 Reply)
Discussion started by: richardjhowlett
1 Replies

2. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

3. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies

4. Red Hat

loghost in etc hosts

Hi, I configure the /etc/hosts in red aht ES 5.4 I want to ask what is the function of "loghost ".. If I miss it , any different or problem ??/ Below is the etc/hosts file 127.0.0.1 localhost 192.168.59.10 A.abc.com A loghost 192.168.59.12 B.abc.com B 192.168.59.13 C.abc.com C (1 Reply)
Discussion started by: chuikingman
1 Replies

5. UNIX for Advanced & Expert Users

NFS and DNS alias

I have an old NetApp filer that exports volumes via NFS for my UNIX hosts. We want to migrate it to the new filer and keep name of the old one as DNS alias to the new filer name with new IP address. The question is will UNIX NFS client that still pointing to the old filer name be able to mount... (5 Replies)
Discussion started by: vostrushka
5 Replies

6. Solaris

loghost could not be resolved

Hi friends, I have seen some really annoying error messages since I have installed Solaris, and solved a few of them, with your help. Now, another message pops up in the middle of my work, and says "loghost could not be resolved" Please help me with it. Here are the details for my solaris... (1 Reply)
Discussion started by: gabam
1 Replies

7. Red Hat

RHEL 5.5, /etc/hosts, multiple loghost entries?

Greetings everyone. I am currently required by company policy to point our servers to a corporate syslog server, so that causes us to have one loghost entry. However the vendor whose software we install on these servers, for their EMS requires us to include another loghost entry. I have searched... (1 Reply)
Discussion started by: msarro
1 Replies

8. Red Hat

DHCP & DNS - Clients get IP but don't register in DNS

I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based. I've installed CentOS 6.2 with... (4 Replies)
Discussion started by: FireBIade
4 Replies

9. UNIX for Dummies Questions & Answers

Create alias files (not alias commands)

If one: $ find -name 'some expression' -type f > newfile and then subsequently wants to create an alias file from each pathname the find command retrieved and the > placed within 'newfile', how would one do this? Ideally, the newly created alias files would all be in one directory. I am... (3 Replies)
Discussion started by: Alexander4444
3 Replies

10. Solaris

DNS client added to DNS server but not working

Hi, We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies
RESOLVER(5)							File Formats Manual						       RESOLVER(5)

NAME
resolver - resolver configuration file SYNOPSIS
/etc/resolv.conf DESCRIPTION
The resolver is a set of routines in the C library (resolv(3)) that provide access to the Internet Domain Name System. The resolver con- figuration file contains information that is read by the resolver routines the first time they are invoked by a process. The file is designed to be human readable and contains a list of keywords with values that provide various types of resolver information. On a normally configured system this file should not be necessary. The only name server to be queried will be on the local machine, the domain name is determined from the host name, and the domain search path is constructed from the domain name. The different configuration options are: nameserver Internet address (in dot notation) of a name server that the resolver should query. Up to MAXNS (currently 3) name servers may be listed, one per keyword. If there are multiple servers, the resolver library queries them in the order listed. If no nameserver entries are present, the default is to use the name server on the local machine. (The algorithm used is to try a name server, and if the query times out, try the next, until out of name servers, then repeat trying all the name servers until a maximum number of retries are made). domain Local domain name. Most queries for names within this domain can use short names relative to the local domain. If no domain entry is present, the domain is determined from the local host name returned by gethostname(2); the domain part is taken to be everything after the first `.'. Finally, if the host name does not contain a domain part, the root domain is assumed. search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it begins with the local domain name, then successive parent domains that have at least two components in their names. This may be changed by listing the desired domain search path following the search keyword with spaces or tabs separating the names. Most resolver queries will be attempted using each component of the search path in turn until a match is found. Note that this process may be slow and will gen- erate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is available for one of the domains. The search list is currently limited to six domains with a total of 256 characters. The domain and search keywords are mutually exclusive. If more than one instance of these keywords is present, the last instance will override. The keyword and value must appear on a single line, and the keyword (e.g. nameserver) must start the line. The value follows the keyword, separated by white space. FILES
/etc/resolv.conf SEE ALSO
gethostbyname(3N), resolver(3), hostname(7), named(8) Name Server Operations Guide for BIND 4th Berkeley Distribution December 14, 1989 RESOLVER(5)
All times are GMT -4. The time now is 11:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy