Project

General

Profile

Actions

Bug #5740

closed

Alias Hostnames Are Not Being Updated

Added by Anonymous almost 10 years ago. Updated almost 10 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/06/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

This used to work great, but recently even after days of waiting, new hostnames added to my alias list are not resolved to their IP addresses and added to the "Diagnostics" -> "Tables" listing.

How can I better troubleshoot this to give you all more information to track this down?

Actions #1

Updated by Chris Buechler almost 10 years ago

  • Status changed from New to Feedback

what's filterdns logging in the resolver log?

Actions #2

Updated by Anonymous almost 10 years ago

Chris Buechler wrote:

what's filterdns logging in the resolver log?

Sorry, I've been out of town. I'll get back to you on this by Monday.

Actions #3

Updated by Anonymous almost 10 years ago

Chris Buechler wrote:

what's filterdns logging in the resolver log?

There are a ton of `failed to resolve`s. When I take one of the "failed" domains and go to Diagnostics -> DNS Lookup, every registered DNS server resolves the domain perfectly fine.

Actions #4

Updated by Chris Buechler almost 10 years ago

They resolved at the time you tried the lookup. They didn't at the point filterdns tried. Does that happen for all hostnames? Even if you put something like 'google.com' in? Does filterdns continue to log "failed to resolve", or is that only at startup, or only at bootup?

Actions #5

Updated by Chris Buechler almost 10 years ago

  • Status changed from Feedback to Not a Bug

looks like a general DNS problem

Actions

Also available in: Atom PDF