I just changed my CentOS server from DHCP to static IP address. After the change, I cannot ping other hosts on the same subnet. (I can ping the CentOS itself).The IP address of CentOS is 192.168.0.202.After pinging 192.168.0.106 (106 is on and other host can ping it), arp -a shows? (192.168.0.106) at <incomplete> on eth0 It looks ARP cannot resolve MAC address of hosts 192.168.0.106.
I bought a network printer, gave it a host name, address should be assigned by my cable or DSL router. Thats what DHCP and DNS is made for right?Now I will print to that printer from my (Lucid) Kubuntu box and resolve it by it's hostname.I can't ping it by printername, I can't ping it by printername.local.It works when I login my router, read out the IP address and hostname the printer registered at the routers DHCP-table and use that address.What can be done that a router transfers the hostnames it has in it's IP-table to clients upon DHCP resolve AND whenever a client get's a new IP-Address?
The little home server of mine has bind configured as a caching dns server. I would like to configure it to resolve local host names. I know dnsmasq can do this, so what would someone need to do to get bind to do this?The network is entirely private with all private IPs which are distributed by dhcpd.(While writing this, the feeling creeps in that it would be easier to just have dnsmasq running.)
1. I have at work a regular LAN with many PCs, each with a DNS-registered public IP. Therefore I am able to address each of these PCs by their fully-qualified names and, for instance, initiate ssh sessions to any of these computers just by typing "ssh <name_of_machine>" from a terminal.
2. Within the aforementioned LAN I have just created a private network with some clients, which access the LAN through a router (a D-link DIR-825). We have created this private network for many reasons, but most importantly because we need to guarantee that the hosts in this network will remain networked among them even if the LAN goes down for any reason (which unfortunately happens often). But we still need to have access to the hosts in the private network from the LAN.
3. I am able to define port forwarding rules in the router in order to access certain services on the private network's clients. For example. I am able to access (by ssh) hosts "H1" and "H2" on the private network from a client on the LAN by defining rules for forwarding ports "P1" and "P2" on the router's public IP to TCP port 22 on the private IPs of "H1" and "H2", respectively. Then I would access each of these hosts from the LAN by using:
4. The problem with the port forwarding approach is that it is not easily scalable. For instance, If I wanted to enable ssh access to each host in the private network, I would have to define a port forwarding rule for each machine, and then REMEMBER all these port rules when initiating a ssh session from the LAN in order to point to the right host. And the problem gets worse when considering more services in addition to ssh.
5. The ideal solution would be to be have a means for addressing each host in the private network individually, in much the same way in which I address the hosts in the LAN (which have DNS-registered names). For instance, in order to access hosts H1 and H2 as in the previous example, i would like to be able to just type
I guess I can say that what I need is some kind of combined DNS-ing and routing that allows me to communicate with the hosts in the private network from outside of it in a transparent way.
The question is: what are any possible solutions for accomplishing this? I have searched the web and found stuff about things like VPNs, reverse-proxies and NAT servers, but I really can't understand if any of these could serve to solve my problem (BTW, isn't my router doing some sort of NAT-ing already? could I just add some DNS-ing in some way?)
I can reach other hosts by means of their global addresses by either the IP address or hostname (that has the global address). What I want to (also) do is have a hostname that references the IPv6 link local IP address (an AAAA record in DNS, or just the fe80::<whatever> address in /etc/hosts) and use that host name in commands to access that host. The problem is, an interface ID is needed when making such a reference.
It sure looks like the programs just pass the host name string on to the resolver library, which does not understand the significance of the '%' even though it could find and see that the name preceding the '%' is consistent with that being an IPv6 link local address (e.g. the logic could have been "split at first % and see if preceeding name is found as a link local address and accept that if so, or ignore the split otherwise" ... but it isn't). Is there a different syntax for this ... or was it overlooked in the design of programming around IPv6?I want to be able to address a host by its link local address, while still using a mnemonic instead of having to type the IPv6 address.
I have an odd thing going on with DNS. I have two machine's running Ubuntu and for some reason they do not always resolved internet addresses on my Internet connection. This has gone on since the Ubuntu 8.04 when I first started using Ubuntu. Anyway, I use OpenDNS' DNS servers and I have been running perfectly.
This is what is odd. My Windows XP Machine never has the problem. It always resolves. Does Windows Possibly have some Microsoft hosted DNS server hard coded in there as a backup? Things are working fine this way so I am not looking to change. I am just a little puzzled and finally got around to asking, "Why is this".
I'm having really weird and frustrating DNS issues with my clients unable to properly resolve the server's ip address. They can resolve each other's, and outside systems, but not the server - at least, not correctly, and not all the time.
I have one Ubuntu server set up that does both DHCP and DNS serving to the Windows systems. The server has DNS forwarding turned on to forward to OpenDNS's servers (I've tried using my ISP's dns servers but the problem remains). The server is *not* set up as a firewall; I am actually using a DLink router for that, and the Dlink is *not* set up to serve up DHCP nor DNS.
What I am getting is that my clients - and there are nothing but Windows clients - will not resolve the name of the server. For example, if I do: ping linuxserver
I get back a false IP address of 192.168.0.64 (and I've seen once a 192.168.2.49).
If, however, I put a dot in there: ping linuxserver.
I get back the *correct* IP address of 192.168.0.2, and thereafter, ping'ng linuxserver without the dot will work. Until the dns cache expires, either naturally or with ipconfig /flushdns on the windows clients.
The client *are* getting valid dhcp leases and can resolve everything happy-happy, they just will not get the proper address of the server 100% of the time.
I'm trying to troubleshoot some strange networking problems. The pattern seems to be that only newer distributions are affected. CentOS 5.4 and Ubuntu 8.04 work fine out-of-the-box. But Arch, Sidux, AntiX, Fedora, etc. show the same pattern of errors.Certain websites cannot be found unless I disable ipv6 in Firefox. And certain addresses cannot be resolved using various terminal commands (wget, apt-get, yum, etc.). What I would ideally like is a permanent solution, perhaps changing some settings on my router, so that I don't have to deal with this each time I test-drive a new distro. I have a hunch the issue has something to do with my DSL provider (Fairpoint) filing for bankruptcy.
One more piece of information that may or may not be relevant: I recently switched a website from one hosting company to another. I noticed there was a delay of several days where I saw the old version at the old host, but viewing the site at a friend's house or the coffee shop showed the new site on the new host. This leads me to suspect DNS issues perhaps, but this is not an area of expertise.
In firefox you can type ubuntuforums and it will bring you here via a google query.Mines stopped working the address bar goes to http://ubuntuforums/ and I get a forbidden page.I've check about : config and all is set fine
Recently my home PC crashed and I had to re-installed it. I put a "clean" install of Fedora11, then copied my /home directory and some other stuff over from the old installation.I have a couple of PHP scripts I wrote, and one of them stopped working. It uses cURL, and when I enable error tracking I get:cURL error number:6cURL errorouldn't resolve host 'www.host.com'I started digging around and I found out Apache doesn't resolve anything at all, so it's not only a cURL problem. For example,
$ip = gethostbyname('host.com'); echo $ip; die();
returns "host.com" and not an IP address.My best guess so far is that Apache has no access to the DNS service (from command line and in browsers everything resolves). had a suspicion it's a SElinux issue and disabled it, but that didn't change anything.I found some old forum posts mentioning problems with chroot-ed Apache, but I haven't done anything to mine and in any case couldn't figure out what the problem was, or the solution, so I'm stuck.
Well, as many proxy applications, GNOME Network Proxy Preferences only allow to ignore hosts. What I want to do is exactly the opposite. I only want to use the proxy for few sites. Is it possible to define only the allowed hosts in any way?
PS: I know FoxyProxy add-on for Firefox does this, but 1)I don't use Firefox and 2)I want the proxy settings system wide not only for browser.
This morning it would not boot; when I tried to wake up the system, it gave me a bunch of errors, the last ones being as follows: "mount error: could not resolve address for servername: No address associated with hostname mountall: mount /media/shares  terminated with status 1" I am writing this in Win 7 since I lost ubuntu. I am using ubuntu 11.04.
What is the (officially) proper way to configure Apache so that a given IP address can have two or more virtual host names, each going to different distinct configurations (e.g. with different DocumentRoot, Alias, etc), and also do this for the IP address so that it goes to a designated configuration rather than defaulting to the first or a random host name?
Apache documentation does not appear to address this. If so, it has it hidden in a non-obvious place.
1) I'm not sure which IP address to use when I list my machine name in /etc/hosts, particularly after reading:
By the w]ay, Arnt Gulbrandsen <email@example.com> says that 127.0.0.1 # should NEVER be named with the name of the machine. It causes problems # for some (stupid) programs, irc and reputedly talk. :^)
Here's what I have now: Code: root@eagleswing:~# hostname eagleswing root@eagleswing:~# cat /etc/HOSTNAME eagleswing.5binc
I'm not certain how to include my router in /etc/hosts so I can use it to link my PCs as stated above. I was thinking of writing (see above link):
192.168.2.1 localbelkin Will this work & is it proper?
3) Do I need to make use of any other IP addresses at this link? What are the WAN IP & Default Gateway addresses used for? I am going to be serving documents & running scripts on Apache.
I have setup Denyhosts to run on my server, and have been using it succesfully for the last few weeks, to allow me to ssh into my server from my home dev machine.
This morning, I accidentally typed my password incorrectly three times - and ended up being locked out of the system (tghat was ok, because that was what was supposed to happen). I logged into the server via another way and took the following actions (in the order given)
/etc/init.d/ssh stop /etc/init.d/denyhosts stop removed my IP address from /etc/hosts.deny /etc/init.d/ssh start
I have DDNS configured and working for dynamic addresses, but it's not quite right for static addresses yet. The DHCP server assigns the static address, but it doesn't update the DNS sever with the associated host name. Which means I have to use the IP address when accessing the host instead of the host name. How can I get the DHCP server to update the DNS with the host name associated with the fixed-address?Here is my current dhcpd.conf.
I am trying to run two web servers (Virtual Hosts) on a single Linux Centos 5.5 box with a single IP address 192.168.0.182. I did all the pre-installation requirements such yum install mysql, yum install mysqladmin, service httpd start, service mysqld start etc etc.In /var/www/html directory, I have two folder called server1 and server2. These two folders have the necessary web server php script files and folders. I opened the browser and managed to install the script on one web server successfully. When I put the IP address 192.168.0.182 on the browser address bar, the page loads without any problem. Now I would like to be able to install the other web server script and I don't know how to?Here is my httpd configuration;
Ubuntu Server 9.10, with apache, proftpd, mysql and the goodies.
I have wordpress installed and setup under /var/www/
The LAN IP address resolves perfectly to the index.php
However I can not get my WAN IP to resolve. My ISP blocks port 80, so I have my router setup to forward port 81 externally to port 80 of my server. I know the port forwarding is setup correctly and working, because I can go to websites like url and test that port 81 is indeed open.
I also have DynDNS setup on my router and through an account with them, to update my IP address with any changes, to a host name. But because port 80 is blocked I have to access it with, host.name.org:81. Ive had this system up and running before with no issues. Now I can not get the host.name.org:81 to resolve.
Neither can I get my ip address xx.xxx.xx.xxx:81 to resolve.
Centos 5, After switching out server to another provider the website responds as it should but the server is unable to establish connections to remote servers. Yes the internet connection is fine, I'm actually working on the server remotely.
--- 220.127.116.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 2999ms /etc/resolv.conf has opendns nameservers nameserver 18.104.22.168 nameserver 22.214.171.124 search localdomain and I've updated /etc/sysconfig/network to reflect the new IP address.
I'm trying to use ssh-keyscan to get some known_host file population going on, but I have a ton of hosts I want to scan, all with multiple aliases in /etc/hosts. Is there a way to use my current /etc/hosts file to do an ssh-keyscan instead of making a special list of hosts that (from what I've read) ssh-keyscan needs?
Currently my OS is Ubuntu 9.04 Jaunty Jackalope Desktop OS and my web server is Apache2. I have a public address 60.x.y.z and my pc local address is 10.x.y.z. I have a web app in my Apache2 which currently run in localhost(10.x.y.z).
I would like to enable the web app so that it could be browse from outside. I know there maybe some port forwarding process and some commands involved in order to do that. But I have no idea on the steps to do that.