Sponsored Content
Operating Systems Linux Red Hat Problem Openvas-setup in CentOs 6.7 ! Post 302973268 by mnnn on Tuesday 17th of May 2016 01:27:39 AM
Old 05-17-2016
Hi
Thanks For Replay
The contents of the file
/etc/resolv.conf

Code:
nameserver 8.8.8.8
nameserver 4.2.2.3
nameserver 192.168.10.15

 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

problem of networking in centos

Hello, I am using dual boot of linux, one is ubuntu and the other is one is centos. I have three NIC's and only one of them connected with cable. The thing is that when I boot from the ubuntu, it does recognize it and I am connected to the Internet. When I boot from the centos I am not... (6 Replies)
Discussion started by: programAngel
6 Replies

2. Linux

How i can setup socks 5 in CentOS?

how i can setup socks 5 in centos? (0 Replies)
Discussion started by: hesamii
0 Replies

3. IP Networking

How i can setup socks 5 in CentOS?

how i can setup socks 5 in centos? (1 Reply)
Discussion started by: hesamii
1 Replies

4. Red Hat

DNS Server Setup Centos 6.5 Issues

I am having a bit of trouble getting my CENTOS 6.5 DNS server to work correctly in our testlab environment. Lab network is 10.8.0.0/24 in which we all access from 10.7.0.0.0/24 && 10.0.0.0/24. Here are my configs: options { listen-on port 53 { 127.0.0.1; 10.8.0.19;}; #listen-on-v6 port 53 {... (2 Replies)
Discussion started by: metallica1973
2 Replies

5. Linux

Unable to access CentOS setup Network Configuration after attempting Python update

I attempted to update Python on my CentOS 5.6 VM and have encountered some issues after then. Initially yum wouldn't work, but I have resolved that. However, now I am unable to access the Network Configuration section under setup. When I do select this option I see this at the command line: ... (2 Replies)
Discussion started by: crmpicco
2 Replies

6. Cybersecurity

Not able to login Openvas after update NVT

Hello, Today, i just updated my Openvas server for latest NVT, portsname and scapdata but after that i am not able to login to my openvas instance. Below command i fired to get this done. openvas-nvt-sync openvas-certdata-sync openvas-portnames-update openvas-scapdata-sync... (0 Replies)
Discussion started by: sunnysthakur
0 Replies

7. UNIX for Beginners Questions & Answers

Problem with cluster on centos 6.5

Hallo to everyone.From sometime i have problems with my asterisk pbx on cent os which is in corosync cluster mode with resource groups.The problem is for time the cluster just swap the active one with the other and the only messages in \var\log\messages is that bond0:link status defenitly down for... (0 Replies)
Discussion started by: evolintend
0 Replies

8. UNIX for Advanced & Expert Users

Issue setup Transparent proxy and Gateway using Squid on CentOS 7

Hello, We are migrating our gateways from CentOS 6 to CentOS 7 and for setting up a transparent proxy using squid and Firewalld i am using below configuration. #Firewalld configurations firewall-cmd --permanent --zone=public --add-forward-port=port=80:proto=tcp:toport=3128:toaddr=LAN_IP... (4 Replies)
Discussion started by: sunnysthakur
4 Replies

9. Linux

Not able to setup CentOS 7 as gateway [Using squid proxy]

Hello, Did anyone setup a CentOS7 as a gateway (with squid transparent proxy). I am trying to do so but not able to setup. I setup squid , iptables (using it instead of firewalld) and all the necessary IPtables rules but nothing work. It work previously but access.log of squid not getting... (4 Replies)
Discussion started by: sunnysthakur
4 Replies
RESOLVER(5)							File Formats Manual						       RESOLVER(5)

NAME
resolver - resolver configuration file SYNOPSIS
/etc/resolv.conf DESCRIPTION
The resolver configuration 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 name-value pairs 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 and the domain name is retrieved from the system. The different configuration options are: nameserver followed by the Internet address (in dot notation) of a name server that the resolver should query. At least one name server should be listed. Up to MAXNS (currently 3) name servers may be listed, in that case the resolver library queries tries 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 followed by a domain name, that is the default domain to append to names that do not have a dot in them. If no domain entries are present, the domain returned by gethostname(2) is used (everything after the first `.'). Finally, if the host name does not contain a domain part, the root domain is assumed. The name value pair 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), named(8) Name Server Operations Guide for BIND 4th Berkeley Distribution September 14, 1987 RESOLVER(5)
All times are GMT -4. The time now is 02:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy