• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Random name resolution failure in named

R

Red Squirrel

[H]F Junkie
Joined
Nov 29, 2009
Messages
9,217
I run my own local DNS, which also acts as a cache/forwarder basically if there's not a local record it just goes out to the root servers to get it. I think it's default behaviour, I don't recall having to change much.

Recently I noticed that it randomly fails to resolve stuff but only external records, local records like my local servers resolve fine. When I'm within my browser it just sits at "looking up [website]" forever. If I do an nslookup, it just outright fails. If I set server to another service like google DNS then it works fine.

I can't seem to find any logs for named, are there any logs somewhere so I can check what's going on or anyone know what would cause these random failures?

I'm doing an update on the server now to rule out some kind of bug, but I did one about a month ago so it's not too old. It got bad enough a moment ago that I could barely even load any website. A restart of the service seems to have fixed it to some extent, but it seems to not last very long till lot of host names fail to resolve again. Worse case scenario I can set forwarders to google DNS or something but just wondering if anyone has any idea why it would be doing this in first place.
 
Ok just decided to setup forwarders to opendns and googledns as backup. Works fine now. Not sure why it was glitching out so much with root servers.
 
Check that you have the correct root servers. We were having an issue and found that an IP address for one of the root servers had changed which was causing issues here and there.
 
Oh that would make sense, have to keep the named.ca up to date once in a while I guess since IPs may change. That may be what was happening, it would randomly try a bad entry.
 
You must log in or register to reply here.
Back
Top