I can connect to my wifi (another laptop is fine on this network), however the browser will not load web pages, and I cannot ping google.com
One strange thing I have noticed is that if I look in /etc/resolv.conf the following lines are present:
#Generated by Network Manager
nameserver 8.8.8.8
nameserver 4.4.4.4
Where I am sure the second line should be 8.8.4.4. So I change the second line to this and check again that the change has been implemented.........which it has.
However, I then reconnected to the wifi and my changes had been wiped and had changed back to:
#Generated by Network Manager
nameserver 8.8.8.8
nameserver 4.4.4.4
Is this behavior normal?
This problem is also intermittent. Sometimes my browser works fine and I can ping google.com, others times I get this problem.
What seems to be the issue?
update:
I can successfully ping google by IP (216.239.39.99)
browser still not able to load websites however.
Wether this is conincidence or not, in my chrome browser I went into advanced settings and turned off the "allow google to predict urls" option and voila I know have internet.
Related
I have DNS problems with my Python scripts, but not with network tools or browser on my Windows 10 desktop.
Running my scripts every network request takes at least 5-10 seconds. Profiling with py-spy with the --idle flag identified socket.getaddrinfo() as the function spent most time in. I tested in the Python REPL with following command:
socket.getaddrinfo("example.org", 80, proto=socket.IPPROTO_TCP)
It took around 5-10 seconds to return. Setting fixed DNS server in my active network interface did change anything.
Rebooting fixes the problem and brings down the respons time below second times. But after keeping the computer up for some days, the problem returns.
It looks like socket.getaddrinfo hits some timeout and then resolves with the correct DNS.
nslookup works just fine. Response time in ms. Also internet surfing in browsers works just fine.
Any ideas where I could start to dig?
What are you trying to accomplish?
Resolving a Domain Name to an IP address?
simply try:
socket.gethostbyname("example.com")
check which dns servers are configured (in cmd- ipconfig /all, DNS Servers category).
Try using a propriety python DNS client, see if the problem persists.
e.g. dnspython
(See this answer -
Socket resolve DNS with specific DNS server)
My domain isn't resolving and I have pinged the IP address but it shows there is 0% packet loss. But when I go to the site in a browser, it can't connect to it.
I've tried for few hours to figure this out, and there is so much information out there but I feel like I've tried it all. I have checked my DNS settings, and I have checked my server logs for errors etc. What could be wrong?
I hope this isn't too much of a noob question, but I am kinda new to DNS stuff. I've done it before but find it hard to figure out the cause if something does go wrong.
In order to troubleshoot DNS issues, here is a list of common troubleshooting steps:
Double-check your DNS settings:
This means checking that your A record(s) is/are correct, and that they point to a valid (and the correct) IP address; checking that your CNAME record(s) is/are correct. Also check other records, if applicable;
Try visiting your website by entering its IP address into the Address Bar of your browser. If you still cannot connect to the site in a browser, it is likely that you are entering the IP address incorrectly, or that your provider is experiencing server or DNS problems, or that your DNS Server is not configured correctly (if you are running your own DNS Server). In this case, I would contact your provider, or go back to the documentation for the DNS Server you are using;
Flush your DNS cache. You can do this by entering the following command at a Command Prompt: ipconfig /flushdns, and then pressing Enter;
Ensure that your Hosts file contains valid entries. You can find out more about the Hosts file at the following address, which also contains a link to download a Hosts file with default configuration:
How can I reset the Hosts file back to the default?
I am in the process of moving the website traffic for adadarters.com from old host to new host. We are keeping old host for various reasons, including mail and ASP files that we don’t want to move, so I simply modified the A record to point to the IP for new host. After 10 hours it has still not really propagated, even though it appears that it has. I have been doing ipconfig /flushdns all day.
What’s happening is that adadarters.com serves up the NewIP (74.220.215.66) and www.adadarters.com serves up the OldIP (65.254.231.127). If you try and type in the URL without www, it appears to redirect to www and sends you to old host.
The way I figured out was nslookup adadarters.com 205.171.3.66 (my ISPs IP address) vs nslookup www.adadarters.com 205.171.3.66.
Also, a traceroute to adadarters.com vs www.adadarters traces the route to new and old IP addresses.
New host says DNS looks fine to them. Old host says settings look fine to them too, and that I just need to wait longer for it to propagate. But why would www propagate differently than non-www? I think they are just putting me off because they don't know (one reason they are the old host).
Any ideas about what might be happening?If by some chance this has resolved by the time you look, the old host files have the logo on right, new has logo on left and is a WordPress site.
This is off-topic here, you should've asked on https://superuser.com/
Your computer probably cached the old DNS. Try ipconfig /flushdns
The problem clearly is not in your ISP's DNS:
$ nslookup www.adadarters.com 205.171.3.66
Server: 205.171.3.66
Address: 205.171.3.66#53
Non-authoritative answer:
Name: www.adadarters.com
Address: 74.220.215.66
I run a high volume website and since yesterday it's not working.
My server (for example) 100.0.0.1 is working fine, I can access WHM etc, rootssh no problem....
Yet none of the domains are working, they say cannot find page.
I have my name server setup at Godaddy using domainname.com
Pointing to 3 IPS, 100.0.0.1, 100.0.0.2, 100.0.0.3
All my domains then have ns1.domainname.com, ns2.domainname.com, ns3.domainname.com
As their Nameserver entries.
This was working fine yesterday, now...nothing.
Any ideas on what I can do? Troubleshoot.
Thank you, I am losing alot of trade as I run an high traffic eCommerce website, so would like to get this fixed as soon as possible.
Have you tried using the IP of the server instead of the domain name? Could roll out a DNS issue. You said you can gain root access fine.
Have you checked your firewall to ensure the correct ports are still open?
If you run a netstat command to check what type of traffic is occurring.
Run this command and then try to access the domain or IP to see if the connection is established or if the service is listening. (watch -n 1 netstat -nat)
I've been developing locally on a little ubuntu netbook with xampp for about 7 months. Two weeks ago I got a computer I'd like to use as a server. I've installed the latest Ubuntu distribution and xampp, moved all my files over, and forwarded port 80. I've also got a domain name from dyndns.com which is being updated by a client which runs in my router (a Netgear WGR6154 v8).
Now, when I try to access my server by typing in the address I got from dyndns.com the browser loads until it timesout. I can access everything locally using localhost as the address so I believe xampp is running, just unable to connect with the internet.
In order to be able to view my files over the internet what should I do next?
Thanks to all in advance...
[I'm starting a bounty for the first person to help me get my files successfully online]
You have a combination of issues here, and that is something of a problem. Each issue is complex in an of itself. Here is what I would recommend to get you going for certain.
First verify that you can surf the web from your server. This will confirm that you have a working ethernet interface.
Step 1 make sure that XAMPP, and your files are viewable from your home network. I assume you are using something like 192.168.1.X for your network and perhaps your server is 192.168.1.10
Go to another computer in your house and type http://192.168.1.10/ and see if you can see your files. If you can then you know that the server is properly configured and XAMPP is working.
Then add an entry to your hosts file to resolve yourdnsrecord.com (or whatever your dyndns record is) to your private ip address. Then when you type yourdnsrecord.com into a browser from that computer you should still get your files. This will rule out your server being improperly configured to listen for that domain name.
Next you need to test to see if there is a firewall problem. To simplify this, first remove your home router from the equation. Instead, place your new server directly onto your internet connection. (assuming you can). This way, you do not need to have NAT or firewalls properly configured. Your dyndns name should map to a public IP and your server should then have that IP and be connected directly to the Internet. If you have your server directly connected, and the command ifconfig from the root prompt returns the same public IP address that your dynamic dns record is point to, then it should work.
It will make your life easier if you have an iphone or some other way to test how your network is seen from the Internet.
If your public IP as shown by ifconfig is different than the IP record in your dyndns account, then your dynamic dns update script is broken. manually set the IP, and see if things work.
It is very possible that this will not work. Some ISPs firewall port 80 preventing their subscribers from hosting servers. Once you have your server directly connected to the internet you can test this (even if your dns is not working) by using the public IP address. As root, type ifconfig from the command prompt to get your public ip address. Then type the command tcpdump -i eth? port 80 from the root prompt. eth? needs to be the same interface that you saw had a public IP address from the ifconfig command. usually this is eth0 but it might be wire0 or something like that.
This command will show you all traffic coming on port 80 to your server.
From an iphone (or whatever second Internet connection you have) browse to the IP address that you got from your ifconfig command. If you see something on your server (and it is directly connected to your ISP) then your ISP is not firewalling you.
If you can get to your server, when it is directly connected to the Internet, either by IP address or by DynDNS address, then your ISP is OK and it is time to debug your firewall.
Two things need to work for your firewall to be configured NAT, where the public address that your router gets from your ISP is converted into your private network and a firewall rule which permits that traffic. If you get this far, then you know your firewall is the problem and then it is just a matter of getting its configuration correct. There are far to many home routers to document here, but you usually can find how-to instructions for your router for this task from the manufacturers website (usually it is part of the manual)
If you follow these instructions exactly you will get your system working. Make comments on the process and I will be happy to modify this to make it clearer.
HTH,
-FT
You should make sure your xampp is not listening to only the localhost.
to do so edit your apache configuration file and check and search for Listen directive
you should be able to know also by analysing the output of netstat -a.
After that make sure your router is forwarding properly, using tcpdump would help.
drop me a comment if you need more help.
Cheers