Two-DNS or dd-dns.de doesn't resolve to IP

Using /e/OS Settings
1

Hi,

I’m using Dyndns with my DSL router for a long time with dd-dns.de (two-dns). Since a couple of month’s, I’ve noticed that my home DSL router is not reachable with a browser from the Internet when using a DynDNS hostname with IPv4 DynDNS address . The router is reachable from my S10 0.23 /e/OS phone with the IPv4-address though. So I’m concluding that DNS hostname resolution is not working on the phone.
DNS hostname does work from home though. I.e. my DynDNS provider seems to have a working service, it’s just that my /e/OS is not resolving this particular domain. It is however resolving any other Internet domains with the browser. So DNS is generally working on /e/OS, but not with dd-dns.de

I’ve tried to change the /e/OS DNS configuration to use 1.1.1.1 or 8.8.8.8 , but that didn’t help.
Do you have an idea why that particular DynDNS provider is not resolving my DynDNS hostname to the IP?
I’ve checked my DynDNS provider and it has the correct IP address of my home DSL router
Thanks & regards,
Hermann

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

2

tl;dr: change provider, desec.io is great

answer would be as simple as “if it doesn’t resolve on the device, its DNS server in use can’t resolve it”. Why it can’t resolve it… maybe the authorative nameserver doesn’t serve?

I picked “some” subdomain at dd-dns.de and saw only one result with the large public resolvers (cloudflare, google, quad9) and authorative servers for the domain crapped out when queried directly. I guess the authoriative one is just overburdened.

~$ dig -t a fritzbox.dd-dns.de @1.1.1.1
fritzbox.dd-dns.de.	60	IN	A	178.203.111.174
~$ dig -t a fritzbox.dd-dns.de @8.8.8.8
~$ dig -t a fritzbox.dd-dns.de @8.8.4.4
~$ dig -t a fritzbox.dd-dns.de @9.9.9.9
~$ dig -t a fritzbox.dd-dns.de @149.112.112.112
~$ dig -t soa dd-dns.de @1.1.1.1
dd-dns.de.		86400	IN	SOA	localhost. root.localhost. 6 10800 3600 604800 3600
~$ dig -t ns dd-dns.de @1.1.1.1
dd-dns.de.		86400	IN	NS	ns2.crns.de.
dd-dns.de.		86400	IN	NS	h2-045.net.crns.de.
~$ dig -t a fritzbox.dd-dns.de @ns2.crns.de
;; communications error to 83.246.76.144#53: timed out
;; communications error to 83.246.76.144#53: timed out
;; communications error to 83.246.76.144#53: timed out
;; no servers could be reached
~$ dig -t a fritzbox.dd-dns.de @h2-045.net.crns.de
;; communications error to 83.246.77.45#53: timed out
;; communications error to 83.246.77.45#53: timed out
;; communications error to 83.246.77.45#53: timed out
;; no servers could be reached

(bogus SOA records, but shouldn’t interfere with queries)

1 Like
3

Thanks for your explanation and hint.
With changing provider you mean DNS resolver. So instead of using the network provider (like O2) for DNS resolution, I would use desec?

I’m asking because desec also seems to offer DynDNS service.

4

no, I mean change the dyndns provider, it doesn’t seem reliable when I poke at it. desec.io does dyndns, sorry I was being unclear

1 Like