meteohub.de

Hello there. I will start with the first.
Currently running a windows AD integrated DNS server
Created hostname for webserver on Linux called "weather.domain.com" (domain is not really the name)
This has a DNS A/Host record with PTR's created in DNS
All machines on my network can "ping" this host name and resolve it to a 192.x.x.x address
My Meteobridge on DLink DIR-505 cannot. Error: wget: unable to resolve host address 'weather.domain.com; (no more tries)

Because I am using virtual directories, I cannot use IP address in place of FQDN.

Network / System shows DNS is 127.0.0.1. I've read other posts as to "why" this is what it is. Don't quite agree with the logic, but ok.....Weather Underground and WeatherBug files upload successfully each time/every time.

Pointed my Meteobridge to a webserver with an IP address only and it worked.

So how can I get this to resolve the host on my LAN? What's interesting is that it is also publicly resolveable in internet DNS as well. So it's def not looking there either.

Thanks in advance for any thoughts.

have you set DNS on meteobridge to your DNS machine?

Yes, in two ways:

Statically assigned an IP address, subnet, gateway and DNS server.
Let DHCP assign the above.

In each case, the DNS server reverts to 127.0.0.1....which from what I ready is "normal"

I've just noticed same problem. System status shows "DNS: 127.0.0.1" after while...
Could that be latest DNS features in the latest release?

That is a OpenWRT related "problem" as they use dnsmasq which has some trouble
in resolving LAN local names when in DHCP client mode.

As long as your Meteobridge does not need to address a machine in your LAN with
a name instead of a fixed IP address this is not a problem at all. So to say less than 0.1%
will be anyhow impacted. As DHCP servers can give devices in your LAN a fixed IP
based on their MAC, it is rather trivial to avoid IPs in the LAN floating around.

Nevertheless I am working on it, to keep you all happy.

BTW, I don't think a headline like "Troubles....many troubles...." is appropriate here
as you just report one "trouble" and it is one easy to circumvent. At least you spared
exclamation marks and capital letters, thanks