ROOT
  • ROOT
  • Example file This is an example
  • duckdns
    • duckdns_not_working
  • general
    • i_have_an_error
  • hassbian
    • Get Hassbian
    • hassbian_config_install_multiple_suites
  • homeassistant
    • breaking_changes
    • confusing_ha_terms
    • Development setup (docker based)
    • Discord webhook
    • easy_le-ssl_duckdns_setup
    • reboot_after_config_change
    • trigger_stuff_with_curl
    • templates
      • get_all_entities_from_a_group
      • list_all_active_domains
      • share_state_between_two_devices
      • strings
      • translate_strftime_weekday
  • python
    • 99_bottles
    • append_to_dict_if_not_allready_there
  • raspberry
    • check_power_trottle
  • windows
    • startup-diskmapping
  • .github
    • PULL_REQUEST_TEMPLATE
      • New Hassbian-config function
    • PULL_REQUEST_TEMPLATE
      • New Suite
    • PULL_REQUEST_TEMPLATE
      • suite_fix_template
Powered by GitBook
On this page
  1. duckdns

duckdns_not_working

PreviousduckdnsNextgeneral

Last updated 6 years ago

/rant_start

This statement is FALSE..

I have seen that statement multiple times and never has that been the case.

DuckDNS is like a phonebook, it has one job and that is to assign a subdomain name to an IP,

If my-ha-domain.duckdns.org resolves to your IP then DuckDNS is working and you should check elsewwhere.

Verify this with nslookup on Windows or a webservice like

nslookup:

C:\Users\user>nslookup my-ha-domain.duckdns.org
Server:  a0d7b954-pi-hole
Address:  192.168.2.200

Non-authoritative answer:
Name:    my-ha-domain.duckdns.org
Address:  127.0.0.1

/rant_end

https://network-tools.com/nslook/