Dyndns update problem after manual reconnect
-
Hello,
i noticed these days that after a manual reconnect of my WAN interface (PPPOE) the corresponding dyndns-entry doesn't get updated. in the logs i see:
"/rc.newwanip: Curl error occurred: Could not resolve host: ddnss.de".
So the update is being called before unbound was restarted and therefore the dyndns update fails. I have to restart that every time manually. Is there any way to make that update happen at a later stage?
Thanks for any help! -
Hello!
By "manual reconnect", do you mean release/reconnect using the buttons on the Status ->Interface page?
Part the the processing sequence in rc.newwanip is :
- reload unbound
- perform RFC 2136 DNS update
- signal dyndns update
- reconfigure IPsec tunnels
- start OpenVPN server & clients
Is unbound running as a straight resolver with no forwarding? No funky dns stuff, like routing dns over a vpn, etc...?
John
-
@serbus
Yes, manual reconnect via the buttons.
Unbound is the resolver, nothing special configured. No dns over vpn too. -
Hello!
Try turning on the Verbose Logging option in that dynamic dns profile and check to see if there are any interesting log entries on either side of the error in the shell or Diag -> Command Prompt :
clog /var/log/system.log | grep -i -C 20 "Curl error occurred"See if that error is popping inside/after a _checkStatus() or _checkLookupStatus() verbose log entry.
Is that a custom Service Type?
John
-
A work around : Domain names exist only for humans.
dyndns scripts are just ... scripts. And don't need domain names, they'll be needing a DNS to transform them to the actual thing : an IP address.
Knowing that ddnss.de stands for :
2001:4ba0:ffe6:1f::1 or 85.114.136.161
you could (always) use an IP.@_igor_ said in Dyndns update problem after manual reconnect:
Unbound is the resolver, nothing special configured
and no 'bloated' pfBlockerNG-devel that can delay the start of unbound ?
-
@Gertjan
Tested with the IP:/rc.newwanip: Sending request to: https://85.114.136.161/upd.php?key=xxxxxx&host=yyyy.ddnss.de
Aug 5 09:17:30 igor php-fpm: /rc.newwanip: Dynamic DNS custom (): _checkStatus() starting.
Aug 5 09:17:30 igor php-fpm: /rc.newwanip: Curl error occurred: SSL: no alternative certificate subject name matches target host name '85.114.136.161'Fails. I have to enter the real dns-name.
Second thing: If i activate in "general setup" the option "DNS-server override" it works again. Strange, i did not use this since years...
So at the moment its working again, but strange - i didn't change config for a long time. So i cannot tell when this begun. Thanks for your help. -
@_igor_ said in Dyndns update problem after manual reconnect:
" the option "DNS-server override" it works again
Which confirms that the Resolver - unbound, locally, is broken / not working.
The override will assign to pfSense the DNS servers (forwarders or resolvers) of your ISP.So, the question is : what is your DNS setup ?
Note : when you install pfSense, "DNS" (using the default build in resolver Unbound) works. What did change it to the no-go state ?
-
@Gertjan Good question! I hadn't any change in my unbound config loooong time. I had to reinstall these days but maintained the config.
Oh, there was a change: From UFS to ZFS. I forgot. Maybe here the problem? I will reset the whole unbound config and set it again. Maybe something in the background flipped away... -
Finally its working again without a DNS-server in "general config"!
I switched every setting in unbound, reconnected, looked at the state of dyndns and somewhere in that process it began working again. I have again all settings as before.
So i think a bit-swap occured somewhere.
Again a very big thanks to all for your great help, which finally stumped me to the right direction!!!!!Case closed.
