DNS issue with wunderground

[36260]

Hello to everyone,
Meteobridge 5.1 (May 6 2021, build 3867), FW 1.4 has been running without a glitch for 173 days. I let it almot unattended. I just checked this morning the upload status tab and was surprised to see this report:

2021-11-20 15:11:25 Error: 2021-11-20 15:11:19 wget: unable to resolve host address 'rtupdate.wunderground.com' (no more tries)

I checked on a windows machine with nslookup. No issues. Then I checked on the unit itself (ssh). nslookup reports:

root@MeteoBridge:~# nslookup rtupdate.wunderground.com
Server: 192.168.21.1
Address: 192.168.21.1#53

Name: rtupdate.wunderground.com
rtupdate.wunderground.com canonical name = prod-pws-ng-ingest.pws-ng-prod- iks-wdc-01-997b58a668d15d562a6bed58ea7c5f9e-0001.us-east.containers.appdomain.cl oud
Name: prod-pws-ng-ingest.pws-ng-prod-iks-wdc-01-997b58a668d15d562a6bed58ea7 c5f9e-0001.us-east.containers.appdomain.cloud
prod-pws-ng-ingest.pws-ng-prod-iks-wdc-01-997b58a668d15d562a6bed58ea7c5f9e-0001. us-east.containers.appdomain.cloud canonical name = pws-ng-prod-iks-wdc-01- 997b58a668d15d562a6bed58ea7c5f9e-0001.us-east.containers.appdomain.cloud
Name: pws-ng-prod-iks-wdc-01-997b58a668d15d562a6bed58ea7c5f9e-0001.us-east. containers.appdomain.cloud
pws-ng-prod-iks-wdc-01-997b58a668d15d562a6bed58ea7c5f9e-0001.us-east.containers. appdomain.cloud canonical name = pws-ng-prod-iks-wdc-01-997b58a668d15d562a6bed58 ea7c5f9e-0001.c00q71dw0bjtihiciel0.akadns.net
Name: pws-ng-prod-iks-wdc-01-997b58a668d15d562a6bed58ea7c5f9e-0001.c00q71dw 0bjtihiciel0.akadns.net
Address 1: 169.63.130.179
Address 2: 169.61.113.58
Address 3: 169.61.113.60
Address 4: 169.55.126.243
Address 5: 169.55.126.244
Address 6: 169.63.130.180
*** Can't find rtupdate.wunderground.com: No answer
root@MeteoBridge:~# nslookup rtupdate.wunderground.com
Server: 192.168.21.1
Address: 192.168.21.1#53

*** Can't find rtupdate.wunderground.com: Parse error
*** Can't find rtupdate.wunderground.com: No answer
root@MeteoBridge:~#

However data is indeed updated on Wunderground. So is there something at stake? I tend not to update if ain't broken.
I would appreciate any advice.
Thank you

[robr57]

Hi,

I reported similar in viewtopic.php?f=61&t=16018

They are looking into it.

[robr57]

In viewtopic.php?f=61&t=16018 one of the issues is closed, but the DNS problem still remains.

I changed the Network config into static from DHCP and tried different DNS servers. I used PiHole, 1.1.1.1, 8.8.8.8 . they all work. But the default DNS from ZiggoVodafone through my Draytek router gives the time out problem in Meteobridge.

I dont understand why, because all other devices in the same network do not have this problem, I tried from Windows, MacOs, iOS , Synology NAS, all DNS diagnostics with NSLookup have no problem with the wunderground dns addresses.

I have no clue what goes on.

[36260]

Thanks robr57. As a matter of fact I’m using a draytek router as well. It is however strange that despite this error, wunderground is updated. And as yourself, tests done on other machins on the same network are trouble free. I think some troubleshooting is needed from dev. What version of meteobridge are you running?

[robr57]

I am on the latest meteobridge 20 november version. Same problem.

[admin]

Looks like robr57's change to opendns solves the issue.

Code: Select all

root@MeteoBridge:~# time nslookup rtupdate.wunderground.com
Server:    208.67.222.222
Address 1: 208.67.222.222 dns.opendns.com

Name:      rtupdate.wunderground.com
Address 1: 169.63.130.179 b3.82.3fa9.ip4.static.sl-reverse.com
Address 2: 169.63.130.180 b4.82.3fa9.ip4.static.sl-reverse.com
Address 3: 169.55.126.243 f3.7e.37a9.ip4.static.sl-reverse.com
Address 4: 169.55.126.244 f4.7e.37a9.ip4.static.sl-reverse.com
Address 5: 169.61.113.58 3a.71.3da9.ip4.static.sl-reverse.com
Address 6: 169.61.113.60 3c.71.3da9.ip4.static.sl-reverse.com
real	0m 0.26s
user	0m 0.01s
sys	0m 0.01s

No idea why the Vigor router does not work fine with some domains.

[36260]

Tried openDNS, same issue. I don't think robr57 said it is solved, isn't it the opposite he reported in the post just above? I understand this is not easy to troubleshoot that kind of issue without having the test gear. I'm open to help on this matter if you think is worth to give a try. Let me know.
I don't know why the post is set as solved. I did not mark it as such.

[admin]

I set it to solved as I was able to check on "robr57" machine and there all issues regarding delayed DNS resolution are completely gone.
If you give me access to your Meteobridge, I can inspect there as well.

If you feel better, I can remove the "solved" tag. No problem.

[36260]

Ok I'll arrange access for you. We did that a while ago. I send you a PM when it is accessible

[admin]

Thanks for giving me remote access. I changed your DNS from using your router' service to use google DNS and all problems are immediately gone.
So my assessment was right, the router's DNS is not working correctly on some domains.

[36260]

Thanks for your time on this issue.