Debian Configuration :: Host Name Resolution Failure?
Aug 15, 2011
I am experimenting with installing a bare minimum, network capable installation of Debian Squeeze. Right now, I am having trouble getting proper host name resolution. I have provided the output of ping (which is able to resolve names), wget (which is unable to resolve names), and the contents of the files I believe to be relevant to the problem. When I installed Debian, I installed *only* the SSH Server from the list of available configurations. Since then, I have installed mdns4, dnsmasq, mdns-scan, and libnss-mdns to get name resolution to work with no success so far. All packages were installed with no recommends -- aptitude -R package name. What am I missing to get host name resolution working?
i have downloaded the pidgin.repo file from the web and copied in /etc/yum.repos.d. and i simply start the yum-updatesd service. When i fire the command yum install pidgin, it gives some name resolution problem. i am accessing net through proxy server.RHEL 5 is my distro. This is what the error msg i am getting.
when i am using traceroute command, it is giving the erro as follow: traceroute [URL]: Temporary failure in name resolution Cannot handle "host" cmdline arg [URL] on position 1 (argc 1)
I am having no luck configuring ProFTPd on a Debian Lenny production server we use to host our MySQL databases and a few websites. I had originally set it up so I could login and manage our internal sites, but I have the need to allow a few clients in to access their sites that we host. I am trying to root the users in their site directory, which would be "/sites/www.whatever.com/".
It just hit me while typing this. Is it possible to create a user without a shell to prevent login via SSH and set the home folder to /sites/whatever instead of /home/username? That would allow me to continue operating with my current configuration and root them in their site while preventing SSH logins.
I'm a beginner + in debian (ie I know how to launch basic command under a shell), and I very new to configuration problem.I have a running perfectly file server for probably more than 2 years that I never touch. That's the debian problem, when it's unning, it's forever, no reboot at all.I recently bought 2 new sata drive 1TB5, that I add to my system by adding to my old system a SATA PCI board without any problem.But, one of these 3 month old drive is already dead.So I try to replace it and that's where problem started.....First I did a#mdadm --manage /dev/md1 --remove /dev/sdb1, of course without sucess because sdb is dead
#mdadm --detail /dev/md1 /dev/md1: Version : 00.90.03
Lately I'm encountering a somewhat annoying malfunction: almost every boot, my desktop is stuck, HD red led is constatnly on, and i get a message from kerneloops that I had a kernel failure. I can move the cursor a little and slowly or not at all. Few violent reboots and I get a clean boot. Running Debian Lenny kernel 2.6.26-2-686 on a Pentium 4 2.0 GHz with 250 MiB ram.
I'm testing to log in using openldap authentication on jessie by following article from [URL] ..... and when I try to log in from ldap client (another debian 8 VM), it failed with
Code: Select allFeb 3 09:25:33 clt nscd: nss_ldap: could not connect to any LDAP server as cn=admin,dc=test,dc=lab - Can't contact LDAP server Feb 3 09:25:33 clt nscd: nss_ldap: failed to bind to LDAP server ldap:///192.168.191.120: Can't contact LDAP server Feb 3 09:25:33 clt nscd: nss_ldap: reconnecting to LDAP server... Feb 3 09:25:33 clt nscd: nss_ldap: could not connect to any LDAP server as cn=admin,dc=test,dc=lab - Can't contact LDAP server
I'm new to Debian and installed it with Cinnamon because I want to learn some OpenCL programming in Linux. I have a Nvidia GT 525M GPU. Once the operating system is installed, I followed [URL] ..... article to install the proprietary Nvidia drivers. As the forum suggested, instead of creating an Xorg server configuration file, I installed Bumblebee according to [URL]..... article.
But when I restarted my machine after completing all the steps when I try to log in I get the follwoing message:
I've just installed 'Testing' on a VMware server and after I completed the install with no problems, the system booted into the kernel and I noticed the following start up process error:
startpar: service(s) returned failure: udev...failure!
I have not seen this before and am not sure if it's related to the fact that this is a virtual machine and not a physical server or something else.
i have this problem i install android sdk, and i install libreries: libstdc++5, lib32stdc++6, lib32ncurses5 and libstdl1.2-dev, now if i use ldd comand don't have problem, but when i use eclipse and i compile a simple example (hello word example), i have this error: [Emulator] SDL init failure, reason is: No available video device i have a notebook toshiba satellite A300-1RI whit ATI Radeon 3650, i install the amd driver and all work well.
3 packets transmitted, 0 received, 100% packet loss, time 1999ms.Same result when using the standard Debian ntp time servers like "server 0.debian.pool.ntp.org iburst" in /etc/ntp.conf.
I have setup a few machines within my house. The Debian Squeeze machines do not provide a host name in the DHCP client list on my router. Strangely, my Ubuntu, Android, and Blackberry machines do show host names. I have noticed the same behavior when wirelessly tethering my Debian laptop to my Android phone (which also uses DHCP). Is there something I need to enable to have the name show up on the router?
I am trying to set up a DMZ host - that is, one multifunctional PC between the WAN and the LAN. I've started with a basic router, and expanding upon that as the need arises. I am currently trying to gain access (from the WAN) to a website hosted on one of the servers in the LAN, but I am having trouble accessing the host from the WAN; I think my iptables configuration may be too restrictive. On the DMZ host, I'm using Debian (Etch). I have setup dhcp3-server, a script to configure iptables and pound (reverse-proxy). The (virtual) machine has 4 network cards: eth0, eth1, eth2, eth3; eth0 is the WAN, eth1 through eth3 serve 3 different virtual LANs.
All machines in the LAN (except one windows 2008 server - I might want to address that problem later) get their IP adresses correctly via dhcp from the DMZ host. All machines on the LAN can access the internet (including the 2008 server if I configure it manually) as they should. If I access http://localhost on the DMZ host, pound reports "The service is not available. Please try again later." - as it should.
I can ping the DMZ host from the WAN on 10.0.0.79 However, if I try to access the DMZ host from the WAN (http://10.0.0.79) I get "Unable to connect" from firefox. I'm sure this is not a pound problem, so I think it's in the iptables, or maybe I should be installing some extra software that I'm unaware of.
I installed a GIMP plugin (David's batch processor gimp) and a lot of packages got updated in the process.
The monitor resolution dropped significantly and going to applications -> system tools -> preferences -> settings -> display gives me the message 'could not get screen information' my webcam and microphone is not recognized anymore either ALT + TAB does not change between open windows. power off does not work. I have to shutdown the system using the command line.
The GUI has changed a lot as well. new color schemes (that I don't really like) file system manager has a completely new look too.
it is very strange. My GRUB screen is still in the old resolution. when the system boots up at some point the resolution changes to the lower resolution.
debian version Code: Select allwim@debian7vaio15:~$ lsb_release -da No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.1 (jessie) Release: 8.1 Codename: jessie
I keep failing at properly configuring my frame buffer.My laptop screen has a resolution of 1440 x 900, so I want 0x036b throughout the whole boot process.However, with my present configuration I have 1440x900 in the grub2 menu and the subsequent 2 seconds, while it displays "Loading Linux 2.6.32-5-amd64"(I reckon this still belongs to grub).
Basically I download to main PC and rsync to my pi as the pi has a fraction of the speed for some reason when downloading form a source outside of my network.
The first few files will sync fine. Then I start getting errors like this
Code: Select allrsync: rename "/data/temp/.File.ext.y1716M" -> "File.ext": No such file or directory (2)
The directory on the host has user and group ownership as pi. Rsync has been setup to login without a password.
Using Debian 5.0 Stable, with all current updates, if I type \192.168.0.249 I get samba access and can use all the shared files ok.if I go via the network the computer should be called \squ-eee-zeboxserver but instead comes up as \SQU-EEE-ZEBOXSERsqu-eee-zeboxserver which when clicked gives the attached error.
my server into the public internet and must have my webserver [2.2.9 (Debian)] act secure. But this does not look very easy [I am searching, reading and working on it already the whole day ]. I read the apache docs, but there is a lot of stuff, which is different in Debian [lenny, 5.0.6]. Apache ignores the host-header given by the browser: [URL] are all served, but should be blocked. I new new to apachy, but on my IIS this works as expected. All browsers act equal [so no browser header problem].I configured two VirtualHosts, an excerpt:
The I go to my hosts file on any box, and add hugo's ip-address under the new name x. Then, x is served, although the host-header in apache Every user coming from the internet could make the same!
I've just installed Debian Squeeze from a live CD. When I open a web browser (be it iceweasel or epiphany) and try to go to google.com, it tells me it can't resolve the host name. [Edit: They do, however, allow me to go anywhere on debian.org, minus the search feature] I also get the same error when I try to go to my website running on a local server. However, when I type the server's IP address (192.168.0.10), it goes to the website fine. Basically, any program I run that needs to resolve a host name returns an error, with the exception of the host command:
I've tried changing my DNS server IP from 192.168.0.1 (my router, configured to provide DNS) to 192.168.1.254 (my internet modem, also configured to provide DNS). That didn't help any. Then I changed my DNS server IP to the same one used by the modem, and now everything works.
I've tried googling my way out of the issue, and I've found where someone had the same issue as I've got and fixed it by adding "blacklist ipv6" to their /etc/modprobe.d/blacklist.conf file, but that didn't work for me.
So, recap: Why does resolving domain names fail for certain applications (except the "host" program) when the DNS server IP is that of my router or modem (which works fine for all of my other computers), but suddenly works when I point the computer straight to my ISP's DNS servers, and how can I permanently fix the problem?
I'm running Debian squeeze on an old IBM laptop with Radeon Mobility 7500 graphic card.In the kernel 2.6.32-5 there is always a little white line at the bottom of the screen.It begins to appear after the font size changes during the boot process.It does not appear in older kernels.
I'm using Debian 5 with Exim 4 on my VPS. My purpose is to make mailboxes for each virtual host on my server. What do I have: 1. Exim is set correctly - receiving mail from [URL]... is successfull. 2. Mail for [URL]... is delivered, and the mail for [URL]... too. But [URL]... is the site written to /etc/hosts (it's localhost), and [URL]... is virtual host. But mail from both boxes writes to /var/mail/mail. Now what do I need: 1. Make mail for [URL]... store in [URL].... and mail for [URL].. store in www/Maildir. 2. Make mailboxes like [URL].... to receive mail by Thunderbird. 3. Set passwords for [URL]... and [URL]... (I don't want to enter my system user/root passwords).
I have a strange iptables issues. I have just built a new Debian install and starting adding some real basic rules (see below) the problem seems to be that the localhost itself can't get any returning traffic. That is, it seems to be allowed outgoing traffic but not the connected, returning traffic. Ordinarily allowing Established Connections would resolve this, see the rule below, but it hasn't. Why this doesn't work. Removing the last DROP in the INPUT chains obviously makes the traffic work!
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A INPUT -j ACCEPT -p tcp --dport 22 iptables -A INPUT -j ACCEPT -s x.x.x.x iptables -A INPUT -j ACCEPT -s x.x.x.x iptables -A INPUT -j ACCEPT -s x.x.x.x -p tcp --dport 80 iptables -A INPUT -j ACCEPT -s x.x.x.x -p tcp --dport 8080 iptables -I INPUT 1 -i lo -j ACCEPT iptables -A INPUT -j DROP
I installed debian etch, it runs and does connect to the internet fine through a linksys router...the linksys router is connected to my cable modem...now..
I just registered for a domain name (ex. mydomainname.org) with Verio....this is where I am stuck.
I installed apache 2, a web server, file server (all seem to work) I need to know what files I need to configure to have my machine actually BE that domain name.
Ex. my linksys DHCP IP addresses, the linksys gets an IP from the cable modem...my yquestion is ONCE I register a domain name with verio...how do I configure my end so it "knows" I am that respective domain name...I think I need to configure the following, but knot sure how to do it: resolv.conf, hosts, and interface?
Trying to set to native resolution of 1360x768 with error "Failed to get size of gamma for output default":
Code: Select allerik@DRAGON:/var/log$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1360 x 768 default connected 1024x768+0+0 0mm x 0mm 1024x768 61.00* 800x600 61.00
[Code] ....
Found these lines in /var/log/kern.log stating "unknown Kepler chipset":
Code: Select allJul 26 17:35:34 DRAGON kernel: [ 15.510099] nouveau ![ DEVICE][0000:03:00.0] unknown Kepler chipset Jul 26 17:35:34 DRAGON kernel: [ 15.510148] nouveau E[ DEVICE][0000:03:00.0] unknown chipset, 0xb06070b1 Jul 26 17:35:34 DRAGON kernel: [ 15.510191] nouveau E[ DRM] failed to create 0x80000080, -22 Jul 26 17:35:34 DRAGON kernel: [ 15.510419] nouveau: probe of 0000:03:00.0 failed with error -22
Google search yielded this bug, which affected GT 730 graphics cards, apparently patched in Linux 3.19:
[URL] ....
Assuming this is the problem, does this mean I have to upgrade to Testing or install proprietary drivers?
Motherboard: M2N-MX with Athlon X2 3600 from 2006 onwards 00:0d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Kernel: Debian Sid with 2.6.32-5-amd64 and custom 2.6.36-rc7 Monitor: Samsung 712N, 17inch, with native 1280x1024 resolution
Everything was fine with both kernels with custom 1280x1024 resolution upto yesterday. But when I rebooted today, first I noticed that X stopped working. After updating xorg.conf to 1024x768, it started working . After going through the kernel log in /var/log/messages, I noticed the following differences
Yesterdays log:
nouveau 0000:00:0d.0: Detected 64MiB VRAM nouveau 0000:00:0d.0: 64 MiB GART (aperture) nouveau 0000:00:0d.0: Saving VGA fonts
[code]....
There is an extra "Load detected" line and the resolution got reduced from 1280x1024 to 1024x768.
I've been scouring the internet for an answer to this problem. I am using Squeeze and have properly configured Grub2 to set my console screen resolution to 1024x768x32 (as per updating /etc/default/grub to contain 'GRUB_GFXMODE=1024x768x32' and updating /etc/grub.d/00_header to contain 'set gfxpayload=keep') and everything works wonderfully. My resolution is set as it should be. However upon installing Xorg (aptitude install xorg ratpoison), my console resolution gets changed to what appears to be 1280x1024.
I thought that this was due to xrandr, however when I issue:
# xrandr -s 1024x768
only the X resolution is changed. When I then CTRL-ALT-F1 back to the console, the resolution is still at 1280x1024 (I am aware that xrandr only affects X, but I assumed that because my console resolution was correct before installing X there might have been some correlation).
I would like for my console resolution to stay at 1024x768 as per Grub2's configuration and for X's resolution to be at 1280x1024.
PS I also noticed that prior to installing Xorg, my CPU boots up without any screen blanking (only for a second or so). However, after installing Xorg, during the boot process the screen does blank briefly. It is at that time that the resolution gets changed to the 1280x1024 setting.
I have 64bit debian 6 squeeze installed on my 64bit pc. I have an NVIDIA gpu which I have installed the drivers for and they work just fine. I also have a 32 bit chroot located at /32 which was created using debootstrap. The NVIDIA 64bit driver gives the option to install compatability driver libraries into the 32bit chroot. Whenever I run any application that uses opengl rendering within the chroot, they segfault. When I uninstalled and reinstalled the NVIDIA driver without installing the libraries to the chroot, and instead replaced them with mesa gl libraries, the programs complain about framebuffer missing. They do not segfault, and some programs that can use sdl instead will work fine. I have xhost + set to allow any programs in the chroot to use the host's xorg. I have the host's proc mounted to the chroot proc directory, and i also have dev mount --bind 'ed to the chroot.
Debian Testing host, Winduhs XP guest. Winduhs is not allowed to directly access The Internets, and I am not setting up bridging as that makes it possible for the guest to mount layer 2 attacks on the LAN. I need for the guest to tunnel through the host without being able to see anything on the host, so it can then get access to The Internets, while being protected by iptables (Shorewall).
Used to be with VMware I had host-only set and the guest in a different class c (192.168.2.1) from the host (192.168.1.1) I turned on ipforwarding, set Shorewall rules, and it all worked. Now I have everything set with VirtualBox, and it does not work. Guest can ping its interface but not host. Host can ping vboxnet0. Host is supposed to masquerade guest's 192.168.2.1 through to the default out at 192.168.1.1, but it's not. I think a clue is in routing, but I don't know what's wrong.
