Server :: Use Resolv.conf To Have A Local DNS Entry?
Jan 10, 2011
I am having a situation where I do not have DNS server (the person who has that is not me) for a few websites which are running on a reverse proxy. I recently after having a long trouble shooting hours found that my proxy pass entries look as follows
I'll preface this by saying i'm by no means an expert on Linux. A competant beginner at most.We have a dedicated server, the 'resolv.conf' was changed, specifically the domain that was listed (this is the primary domain).I only became aware of this change, when we get into work on Friday and all our sites were down - I attributed this to DNS fault as if I changed my host file (I work on a windows machine) and specifically routed to the domains to the correct IP address, the websites were served fine.I tracked down the resolv.conf change by quizzing a collegue. I then switched the resolv.conf file back to it's original state - luckily a backup was made so I am 100% sure that the current resolv.conf is the correct one.
change was made Friday morning, around 9.30am (UK time). It is now 5.05pm (UK time). The original change was made sometime on Weds afternoon, and the sites stopped serving between Thursday night and Friday morning.Does anyone have any idea how long it should take for the fix to be picked up? Will it be picked up? I just started to think that the change can't be picked up due to some DNS related voodoo.
I am running an application that requires use of my /etc/hosts file. In it, I have my machine name and its LAN ip address. The program creates a service on a specific port, then attempts to connect to it based on the host name. So my hosts file has to be correct.I added the nameservers to resolv.conf and now my application will not run. My guess is that the computer is checking the name servers first, timing out then checking the hosts file.Is there a way I can tell the system to check the hosts file first, then DNS. I thought it should behave that way by default, but it does not appear to.
My Debian workstation is on a predominantly Windows network. It is resolving internet addresses (i.e. www.google.com, etc) just fine. However it's not resolving any of the address of machines on the local network and the windows machines do not resolve the linux machines address either. All machines (linux and windows) can access each other just fine via direct IP reference.
My /etc/resolv.conf file has the following IP addresses listed:
127.0.0.1 10.1.1.111 10.1.3.4
10.1.1.111 is a netgear VPN/router that is the primary router for the LAN and maintains a VPN to a remote office 10.1.3.4 is the IP address of the Windows Primary Domain control on which the DNS server is running. That server is at the remote office. The system acts like it is completely ignoring anything I put in the resolv.conf file. From the linux X server I'm using "Network Setting" utility to make changes to the network configuration. This appears to work fine for things like switch between DHCP and static IP.
I use Fedora 13 (minimal installation), ISC DHCP server 4.1.1-P1. I'm running Fedora 13 too on a separate machine (minimal installation) with ISC DHCPclient 4.1.1-P1. My goal is to do some IPv6 testing. When I use the DHCP client manually (dhclient -6 -timeout 5 -d -v eth0), the client retrieves and installs a dynamically assigned IPv6 address.
Additionally, the client gets 1 DNS resolver address and 1 DNS search list. The resolver address and DNS search list always get written into /etc/resolv.conf. Perfect, exactly what I need. But when I do a "service network restart" or restart my system (which should trigger the same, as far as I understood), the DNS resolver addr and the search list get written into /etc/resolv.conf.save and the /etc/resolv.conf stays as before. How can I change this behavior? I don't need the .save file, I just want to have /etc/resolv.conf replaced by the latest DNS information.
I'm setting up virtual dev environments and I want the hostname.domain to be something specific, eg- "barney.local". However my /etc/resolv.conf file keeps getting nuked because i'm using DHCP. I placed this into my dhclient.conf:
How can I keep /etc/resolv.conf static ... as in preventing it from being changed by the network manager ... without actually disabling the network manager (so wireless users can get their wireless setup that includes IP address, but leave the resolver configuration as is)?
I tried to setup a dyndns, and ever since I tried to get that setup, I can't access my webmin, or access /etc/hosts/resolv.conf. But I can still access my samba shares I had created before this happened.
I need help figuring out why my resolv.conf keeps changing to this, causing me to not be able to access the outside internet and only the local network.I thought I fixed it by getting rid of the loopback interface and adding in the eth0 interface in /etc/network/interfaces URl...And then things would work temporarily, and eventually the nameserver in resolv.conf would get reverted again.
I am using kubuntu 9.10 64-bit on AMD M500 machine i removed networkmanager (because i had frequent disconnect) and installed wicd but the /etc/resolv.conf had a comment on top which says that it is to be configured by networkmanager (still) I put the DNS in there manually and it works What to put in there so that it uses DHCP ? Maybe its set to be not written by anyone other than networkmanager ??
As you may well be aware the resolv.conf search appears to be limited to 6 domains. I need 7 One thing I noticed is that if you run nslookup on a short name that is in the 7th search it does work but ssh does not. I'm guessing that nslookup is actually reading the whole file and isn't limited.
When I boot my computer (Ubuntu 9.10) /etc/resolv.conf is written as:# Generated by Connection Managernameserver 10.33.8.11 10.33.4.136However, if I try to do anything from the command line, I get an error like:host: parse of /etc/resolv.conf failedI then need to edit /etc/resolv.conf to:
# Generated by Connection Manager nameserver 10.33.8.11 nameserver 10.33.4.136
As I understand it, /etc/resolv.conf is rewritten at boot time by NetworkManager (a script?)I have a problem in the order the nameserver entries are written by my system (F13). This is:
I have been trying to follow this guide for dnssec http://wiki.debian.org/DNSSEC in which at the very last it gives that you should change the value in /etc/resolv.conf to 127.0.0.1 Now in mine, network-manager overwrites the values. Is there a way to stop network-manager from overwriting the values in /etc/resolv.conf ?seems the simplest is to write-protect it. chattr +i /etc/resolv.conf
I "fixed" my Lenny home server bind9 configuration because my resolv.conf was always overwritten loosing configuration. The fix involved adding the following to /etc/resolvconf.resolv.conf.d.base.
##base file at /etc/resolveconf/resolveconf.d/base nameserver 127.0.0.1 nameserver 192.168.1.4
I'm trying to set this open-nic-dns (69.164.208.50) as default (instead of 192.168.2.1 - router-ip). So if I try to edit /etc/resolv.conf to this nameserver - but if i restart it's 192.168.2.1 again.
I'm having problems with my resolv.conf file. Every time I reboot my computer it goes blank and I have to re-type it before I can get on the network. How do I prevent it from being overwritten?
I am using KVPNC (recommended by the VPN owner) on Ubuntu 9.10 using my Universities direct Ethernet connection.
I have downloaded all the .ovpn scripts to a directory. I have downloaded KVPNC from the repository (apparently for 9.10 you do not download from the KVPNC website).
I then use sudo kvpnc and select a server (since there are many based on the .ovpn files).I click connect and the script works and tells me I have a connection. See below for an example. All appears to work.
But when I actually load any Internet program e.g. Firefox it cannot find a website.This happens for all servers which have different locations around the world.When I disconnect KVPNC I still have no access. I have to remove the Ethernet cable before it works again.
debug: Connect try requested, profile: Stockholm, type: OpenVPN debug: openvpn: /usr/sbin/openvpn debug: Support for TUN/TAP found (compiled into kernel or kernel module already loaded). debug: Default interface: "eth0". debug: IP address of default interface: "my IP address". code....
I realise there are errors e.g. the /etc/resolv.conf must be a symlink but have tried doing this and still have exactly the same issues.
I'm using 9.10 Ubuntu Karmic 64-bit (but same thing happens on my 32 bit VM on same PC).
My /etc/resolf/conf file is not updated with DNS information on first boot. The DNS information is in the /etc/network/interfaces file.
The trick I have to do every time I reboot the PC is:
Code: sudo ifdown eth0 && sudo ifup eth0
First off, why? Second how can I resolve this issue?
I have three NICs eth0 and 1 are normal LANs connected to the internet, but I choose eth0 as the primary. eth2 is a local private one. the DNS information from eth0 should be in the resolv.conf file but isn't. The file is empty at bootup, except for some comments instructing me not to edit this. After running the above sudo commands the file is properly updated and internet works.
Here's my /etc/network/interfaces file's contents:
Code: auto lo iface lo inet loopback auto eth0 #iface eth0 inet dhcp
The local DNS server is slow, so I added the openDNS servers to /etc/dhcp3/dhclient.conf. But Network manager keeps appending the local DNS server to resolv.conf. I need to pick up a DHCP address but how to stop it changing DNS servers?
My network works before but now it has follow issue, when I ping google.com, I got Quote:
ping: unknown host google.com but my network still works partially because I can still connect to a DNS listed in my /etc/resolv.conf to get host google.com's ip adress by Quote:
host -t a google.com ip.of.one.dns and then I ping the returned IP result 66.249.89.104, the ping works fine. the issue is that I can't connect to Internet, what I can remember is that I ever removed /etc/resolv.conf and this file was created again by network-manager, and I already verified the two dns IPs listed in the resolv.conf are both correct and works fine with command host.
I am trying to edit my /etc/resolv.conf file while under root. After saving the changes and reboot my computer, file has not changed. I read a thread on chattr and lsattr on this fourm.(see link below) I ran in terminal lsattr /etc/resolv.conf and got the following results:-----------------e- /etc/resolv.confWhat does the dashes and e mean? I thought I would get ----ia------------ /etc/resolv.conf instead, as shown in the link. What am I doing wrong?
Every time my workstation reboots I have to manually redo my resolv.conf file because some of the servers I manage use apparently different nameservers than what my system is registering at boot. Is there a way to make sure my resolv.conf file says static?
I have an Ubuntu 10.04 server. It gets its IP address by DHCP (the router has a fixed reservation so it always gets the same one). However, it needs its nameserver to be itself, and not the DNS servers given out by the router. How can I make dhcp not overwrite resolve.conf?
(Yes I know I could just set a static IP. But I'm testing stuff out here, and want to know if it can be done without doing that.)
The problem is that the above resolv.conf file doesnt work anymore. The only way that our workstations get name resolution is by commenting out the second and forth lines, which happen to be our secondary DNS. This has got me confused because why would resolv.conf be broken by having a secondary nameserver and search path? Shouldnt it just use the first nameserver unless it fails to resolve? Almost seems like just having the secondary in the file breaks name resolution. I cant ping local hosts or anything on the internet unless I do this:
my rounter causes puppy to write an improper dns entry in resolv.conf. Consequently I have to manually write it, then I have to place a command on it to make sure it doesn't get rewritten on boot, or after a couple of hours use. I had this problem with xubuntu as well.
[URL]
I solved this problem in ubuntu by using the chattr command.
[URL]
Puppy won't let me do this. When I use the chattr +i /etc/resolv.conf, it gives me this error. chattr: Inappropriate ioctl for device while reading flags on /etc/resolv.conf I tried chmod 444 but it had no effect on reboot. resolv.conf was rewritten again. How can I make sure this file does not get rewritten. Why won't chattr work?
