Fala pessoal, bom dia. Instalamos como teste em um cliente a versão 2.2 RC e logo em seguida aplicamos a versão RELEASE. Tudo correu bem, com load balance, regras e o próprio sistema em si.
Porém, não há manobra que dê jeito de atualizar o DNS dinâmico para este cliente. Como ele possui dois links com ips dinâmicos, preciso disto para monitorá-lo e prestar o suporte necessário. De toda forma, os hosts sempre resolvem 0.0.0.0 e não atualizam. As entradas de host e ips foram devidamente substituídos para não popular informações demais ;) ==================================== Jan 28 10:15:45 php-fpm[25317]: /rc.dyndns.update: DynDns: updatedns() starting Jan 28 10:16:19 php-fpm[25317]: /rc.dyndns.update: DynDns ( dyndns1.homelinux.com): x.x.x.x extracted from checkip.dyndns.org Jan 28 10:16:19 php-fpm[25317]: /rc.dyndns.update: DynDNS ( dyndns1.homelinux.com): running get_failover_interface for opt1. found re1 Jan 28 10:16:37 php-fpm[25317]: /rc.dyndns.update: DynDns ( dyndns1.homelinux.com): x.x.x.x extracted from checkip.dyndns.org Jan 28 10:16:37 php-fpm[25317]: /rc.dyndns.update: DynDns ( dyndns1.homelinux.com): Current WAN IP: x.x.x.x Cached IP: 0.0.0.0 Jan 28 10:16:37 php-fpm[25317]: /rc.dyndns.update: DynDns ( dyndns1.homelinux.com): DynDns: cacheIP != wan_ip. Updating. Cached IP: 0.0.0.0 WAN IP: x.x.x.x Jan 28 10:16:37 php-fpm[25317]: /rc.dyndns.update: DynDNS ( dyndns1.homelinux.com): DynDns _update() starting. Jan 28 10:16:37 php-fpm[25317]: /rc.dyndns.update: DynDNS: ( dyndns1.homelinux.com) DNS update() starting. Jan 28 10:16:37 php-fpm[25317]: /rc.dyndns.update: DynDNS ( dyndns1.homelinux.com): DynDns _checkStatus() starting. Jan 28 10:16:37 php-fpm[25317]: /rc.dyndns.update: DynDNS ( dyndns1.homelinux.com): Current Service: dyndns Jan 28 10:16:37 php-fpm[25317]: /rc.dyndns.update: phpDynDNS ( dyndns1.homelinux.com): PAYLOAD: nohost Jan 28 10:16:37 php-fpm[25317]: /rc.dyndns.update: phpDynDNS ( dyndns1.homelinux.com): (Unknown Response) Jan 28 10:16:39 php-fpm[25317]: /rc.dyndns.update: DynDns: updatedns() starting Jan 28 10:16:39 php-fpm[25317]: /rc.dyndns.update: DynDns ( dyndns2.homelinux.com): y.y.y.y extracted from checkip.dyndns.org Jan 28 10:16:39 php-fpm[25317]: /rc.dyndns.update: DynDNS ( dyndns2.homelinux.com): running get_failover_interface for wan. found re2 Jan 28 10:16:51 php-fpm[25317]: /rc.dyndns.update: DynDns ( dyndns2.homelinux.com): y.y.y.y extracted from checkip.dyndns.org Jan 28 10:16:51 php-fpm[25317]: /rc.dyndns.update: DynDns ( dyndns2.homelinux.com): Current WAN IP: y.y.y.y Cached IP: 0.0.0.0 Jan 28 10:16:51 php-fpm[25317]: /rc.dyndns.update: DynDns ( dyndns2.homelinux.com): DynDns: cacheIP != wan_ip. Updating. Cached IP: 0.0.0.0 WAN IP: y.y.y.y Jan 28 10:16:51 php-fpm[25317]: /rc.dyndns.update: DynDNS ( dyndns2.homelinux.com): DynDns _update() starting. Jan 28 10:16:51 php-fpm[25317]: /rc.dyndns.update: DynDNS: ( dyndns2.homelinux.com) DNS update() starting. Jan 28 10:16:52 php-fpm[25317]: /rc.dyndns.update: DynDNS ( dyndns2.homelinux.com): DynDns _checkStatus() starting. Jan 28 10:16:52 php-fpm[25317]: /rc.dyndns.update: DynDNS ( dyndns2.homelinux.com): Current Service: dyndns Jan 28 10:16:52 php-fpm[25317]: /rc.dyndns.update: phpDynDNS ( dyndns2.homelinux.com): PAYLOAD: nohost Jan 28 10:16:52 php-fpm[25317]: /rc.dyndns.update: phpDynDNS ( dyndns2.homelinux.com): (Unknown Response)x.x.x.x =========================================== O DNS forwarder está funcionando perfeito e a recomendação de fazer o override dos DNS pelos da WAN/PPPoE já fiz tamém. Nada deu certo. Alguém já pegou este tipo de problema atualizando para a 2.2? Qualquer ajuda é bem vinda. Um abraço, Atenciosamente, Fábio Fraga Machado Diretor de Tecnologia e Infraestrutura Data Space Networks & TI : Telefone: (48) 4052-9252 : MSN: [email protected] : GTalk: [email protected] _______________________________________________ Pfsense-pt mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/pfsense-pt
