HomeLatest ThreadsGreatest ThreadsForums & GroupsMy SubscriptionsMy Posts
DU Home » Latest Threads » Forums & Groups » Topics » Computers & Internet » Computer Help and Support (Group) » Weird DNS/firefox under l...

Sat Jun 28, 2014, 07:25 AM

Weird DNS/firefox under linux problem

Ok, I'm hoping someone can tell me where to go to change a setting or config so this quits happening.

I use firefox under fedora, and it seems like every time I have trouble getting DNS, firefox suddenly decides that whatever website I was trying to reach should simply be assigned to my own IP address. And refreshing won't help, it then has decided that my IP IS the correct IP for that website until I kill off firefox and restart it. Iirc, even doing 'server network restart' doesn't even fix the issue unless I've also done a killall on firefox, so wherever the screwed up DNS mapping is being kept, it's in memory used by the browser, not by the system.

Any ideas? I've had these same problems across multiple versions of both the browser and the OS.

4 replies, 1705 views

Reply to this thread

Back to top Alert abuse

Always highlight: 10 newest replies | Replies posted after I mark a forum
Replies to this discussion thread
Arrow 4 replies Author Time Post
Reply Weird DNS/firefox under linux problem (Original post)
Erich Bloodaxe BSN Jun 2014 OP
discntnt_irny_srcsm Jun 2014 #1
Drew Richards Jun 2014 #2
Erich Bloodaxe BSN Jun 2014 #3
Drew Richards Jun 2014 #4

Response to Erich Bloodaxe BSN (Original post)

Sat Jun 28, 2014, 09:01 AM

1. I'm not certain...

...why this would happen with firefox but you could try using opendns rather than your gateway for dns service.
This might solve your problem and if you're using a home network with a router, this may speed your browsing a bit.
If you travel with your pc, you may have to change this back as some public networks demand you login, accept their TOS... Those networks often redirect you to these pages by intercepting web traffic which can't happen if you've replaced the gateway/dhcp configured dns addr.

http://www.opendns.com/opendns-ip-addresses/
https://support.opendns.com/entries/26272175-Introduction-to-Configuring-OpenDNS

Reply to this post

Back to top Alert abuse Link here Permalink


Response to Erich Bloodaxe BSN (Original post)

Sat Jun 28, 2014, 06:16 PM

2. Correct me if im wrong but it sounds like you are obtaining your ip via dhcp...if this is the case

The your router or modem might not have decent dns injection settings...

Preferably you want to hard code your dns on you linux box in your resolve.conf file...try using googles servers first not loopback...

8.8.8.8
4.4.4.4

Then leave loopback as last

127.0.0.1

Same goes if you have a modem or router providing dhcp ip to your box you need to make sure it is injecting more dns than just your internet providers dns..it could be flaky..

Drew.

Reply to this post

Back to top Alert abuse Link here Permalink


Response to Drew Richards (Reply #2)

Sat Jun 28, 2014, 09:03 PM

3. I do have DNS hardcoded in resolv.conf.

With the local roadrunner business class DNS addresses. (I've got the teleworker package, since I need a fixed IP to run a server off of here at home as well.)

I'll check the router as well, but I thought I had it hardcoded as well. Maybe not. I'll have DNS for a while, then it goes flaky for brief periods (often just long enough to screw up one website) then work for the very next website I try, while still leaving the first one I tried mucked up.

Reply to this post

Back to top Alert abuse Link here Permalink


Response to Erich Bloodaxe BSN (Reply #3)

Sat Jun 28, 2014, 09:12 PM

4. Dump roadrunners dns a try setting googles see if its road runner dns's failing and making you

Be redirected to loopback on the modem...

As in roadrunner didnt set up you modem you are being injected dns from their connection rather than being coded on your rr router...and when it fails the dhcp injects the only thing configured on the router...ie loopback 127.0.0.1

Again that sounds like what you are describing...

A dns lookup failure and the secondary or terciary look up becomes lookback then that gets caught in your cache for whatever page failed...

Reply to this post

Back to top Alert abuse Link here Permalink

Reply to this thread