/etc/resolv.conf problems

Reasons · 2008-01-09 19:45:14

In my conky script, the gmail portion stopped working so I just tried to do a normal wget https://mail.google.com in the terminal. The output was

--11:41:41--  https://mail.google.com/
           => `index.html'
Resolving mail.google.com... 1.0.0.0
Connecting to mail.google.com|1.0.0.0|:443...

which obviously isn't right. What could have changed? I use WICD to connect to my network.

rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=(sky2 iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore acpi-cpufreq cpufreq_conservative)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="reasons"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dhcp"
wlan0="dhcp"
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(lo eth0 wlan0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)

#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng crond dbus netfs !network !dhcdbd wicd @cups @alsa @acpid @hal @fam @mpd @acpid @cpufreq gdm)


# End of file

/etc/hosts

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>    <hostname.domain.org>    <hostname>
127.0.0.1        localhost.localdomain    localhost reasons

# End of file

Last edited by Reasons (2008-01-11 01:28:45)

Reasons · 2008-01-09 20:32:09

It's looking to be something along the lines of wicd not updating /etc/resolve.conf. It was happening in another thread. Grabbing the testing version and I'll report back.

EDIT - Didn't change a thing.

Last edited by Reasons (2008-01-09 21:13:00)

Reasons · 2008-01-11 01:29:07

Trying out kde now but the problem is still there, not that I thought it'd make adifference.

search domain.actdsltmp
nameserver 192.168.0.1
nameserver 205.171.3.65

Last edited by Reasons (2008-01-11 01:30:14)

jacko · 2008-01-11 13:32:35

nameserver 192.168.0.1

that is not a nameserver that I am aware of... Do you need that for wlan or something? Otherwise I'd get rid of that for starters.

Last edited by jacko (2008-01-11 13:32:48)

vacant · 2008-01-11 13:50:24

jacko wrote:

nameserver 192.168.0.1
that is not a nameserver that I am aware of... Do you need that for wlan or something? Otherwise I'd get rid of that for starters.

If it is the lan address of the router, it should work just fine.

ralvez · 2008-01-11 14:08:51

reasons,

You are using dhcp in your LAN, so to test the problem you can remove (read back-up first) /etc/resolv.conf and restart your DHCP server.
If things are working as they should you should get a new "/etc/resolv.conf" and a correct set of "nameservers". If you get the wrong set take a look at your router configs.

Hope this helps.

R.

Reasons · 2008-01-11 14:23:31

Remove as in empty the file or as in delete?

Reasons · 2008-01-11 17:33:19

Well before I did anything, I had to go off to class and there everything worked find, so it is something to do with router. The only problem is, I don't know any settings for it. Is there a way to find out?

ralvez · 2008-01-11 22:57:18

Well ... it may be.
The first thing is that you tell us what router you have then we will see what can be done.

R.

underpenguin · 2008-01-11 23:27:10

I was having the problem of resolv.conf containing the IP of the router. I put opendns ip's in resolv.conf and added a -R (don't overwrite) option to my dhcpcd options.

Reasons · 2008-01-12 01:57:04

Actiontec GT701-WG
underpenguin, how would I go about doing that?

Zer0 · 2008-01-12 19:26:36

nameserver 192.168.0.1

shouldn't be and issue if you have a router. The router should handle DNS forwarding to your ISP assigned DNS servers.

ralvez · 2008-01-12 19:51:42

Log into your router. In a browser type : 192.168.0.1 and you will enter the router configuration tool.
Click on the "Advanced Setup" tab then select on the side bar "DHCP Settings" and verify your settings and that the only nameserver used are the ones provided to you by your Isp.

Hope this helps.

R.

note: Actually I presume you have DNS:Dynamic, so choose DNS:STATIC then fill the DNS1 and DNS2 with the nameservers from your ISP and you are done.

Last edited by ralvez (2008-01-12 19:55:03)

Reasons · 2008-02-18 19:18:06

I tried that all to no avail. The problem actually went away for a while but now it is back. I've disabled ipv6 which is what solved it but now that isn't working. Also,

[shawn] /etc/rc.d/dhcpd start
:: Starting DHCP Server [FAIL]

Last edited by Reasons (2008-02-18 19:36:42)

nawcom · 2008-02-19 02:41:36

i was wandering around forums and i noticed the wicd issue with archlinux, since it still focuses on dhcpcd, not dhclient - so resolv.conf doesnt upload.
http://bbs.archlinux.org/viewtopic.php? … 34#p332334

let me know if it solves the issue.

Cerebral · 2008-02-19 02:47:29

Reasons wrote:

I tried that all to no avail. The problem actually went away for a while but now it is back. I've disabled ipv6 which is what solved it but now that isn't working. Also,
[shawn] /etc/rc.d/dhcpd start
:: Starting DHCP Server [FAIL]

Is there a reason you're starting the dhcp Server, and not client? Do you want dhcpcd?

Reasons · 2008-02-19 03:10:47

nawcom wrote:

i was wandering around forums and i noticed the wicd issue with archlinux, since it still focuses on dhcpcd, not dhclient - so resolv.conf doesnt upload.
http://bbs.archlinux.org/viewtopic.php? … 34#p332334
let me know if it solves the issue.

That fixed it, thanks. Let's hope it stays this time.

Cerebral wrote:

Reasons wrote:
I tried that all to no avail. The problem actually went away for a while but now it is back. I've disabled ipv6 which is what solved it but now that isn't working. Also,
[shawn] /etc/rc.d/dhcpd start
:: Starting DHCP Server [FAIL]
Is there a reason you're starting the dhcp Server, and not client? Do you want dhcpcd?

That was my mistake.

Arch Linux

#1 2008-01-09 19:45:14

/etc/resolv.conf problems

#2 2008-01-09 20:32:09

Re: /etc/resolv.conf problems

#3 2008-01-11 01:29:07

Re: /etc/resolv.conf problems

#4 2008-01-11 13:32:35

Re: /etc/resolv.conf problems

#5 2008-01-11 13:50:24

Re: /etc/resolv.conf problems

#6 2008-01-11 14:08:51

Re: /etc/resolv.conf problems

#7 2008-01-11 14:23:31

Re: /etc/resolv.conf problems

#8 2008-01-11 17:33:19

Re: /etc/resolv.conf problems

#9 2008-01-11 22:57:18

Re: /etc/resolv.conf problems

#10 2008-01-11 23:27:10

Re: /etc/resolv.conf problems

#11 2008-01-12 01:57:04

Re: /etc/resolv.conf problems

#12 2008-01-12 19:26:36

Re: /etc/resolv.conf problems

#13 2008-01-12 19:51:42

Re: /etc/resolv.conf problems

#14 2008-02-18 19:18:06

Re: /etc/resolv.conf problems

#15 2008-02-19 02:41:36

Re: /etc/resolv.conf problems

#16 2008-02-19 02:47:29

Re: /etc/resolv.conf problems

#17 2008-02-19 03:10:47

Re: /etc/resolv.conf problems

Board footer