starred/ddns-updater
1
0
Fork 0
mirror of https://github.com/qdm12/ddns-updater.git synced 2026-08-02 10:38:41 -04:00
Code Issues 312 Packages Projects Releases 10 Wiki Activity

name.com IP update sent creates a duplicate entry and does not update the current entry : name.com creating record: bad request sent: Parameter Value Error - Duplicate Record #402

New Issue
Closed
opened 2025-11-20 04:23:37 -05:00 by saavagebueno · 16 comments
saavagebueno commented 2025-11-20 04:23:37 -05:00
Owner
Copy Link

Originally created by @CaptainBuzzable on GitHub (May 17, 2024).

TLDR: Failure (creating record: bad request sent: Parameter Value Error - Duplicate Record) name.com

  1. Is this urgent: Yes

  2. DNS provider(s) you use: name.com

  3. Program version:

    qmcgaw/ddns-updater:2.6.0

  4. What are you using to run the container: docker-compose

  5. Extra information (optional)

  6. qmcgaw/ddns-updater:2.6.0

Logs:

Failure (creating record: bad request sent: Parameter Value Error - Duplicate Record) name.com
xxxxxx.xxxx  | 2024-05-16T15:05:56Z ERROR creating record: bad request sent: Parameter Value Error - Duplicate Record

Configuration file (remove your credentials!):

   {
      "provider": "name.com",
      "domain": "xxxxxx.com",
      "host": "@",
      "username": "xxxxxx",
      "token": "xxxxxxxxxxxxxxxx",
      "ttl": 300,
      "ip_version": "ipv4",
      "ipv6_suffix": ""
   }

Host OS: Ubuntu Docker

Originally created by @CaptainBuzzable on GitHub (May 17, 2024). <!-- YOU CAN CHAT THERE EVENTUALLY: https://github.com/qdm12/ddns-updater/discussions --> **TLDR**: *Failure (creating record: bad request sent: Parameter Value Error - Duplicate Record) name.com* 1. Is this urgent: Yes 2. DNS provider(s) you use: name.com 3. Program version: <!-- See the line at the top of your logs --> `qmcgaw/ddns-updater:2.6.0` 4. What are you using to run the container: docker-compose 5. Extra information (optional) 6. qmcgaw/ddns-updater:2.6.0 Logs: ```log Failure (creating record: bad request sent: Parameter Value Error - Duplicate Record) name.com xxxxxx.xxxx | 2024-05-16T15:05:56Z ERROR creating record: bad request sent: Parameter Value Error - Duplicate Record ``` Configuration file (**remove your credentials!**): ```json { "provider": "name.com", "domain": "xxxxxx.com", "host": "@", "username": "xxxxxx", "token": "xxxxxxxxxxxxxxxx", "ttl": 300, "ip_version": "ipv4", "ipv6_suffix": "" } ``` Host OS: Ubuntu Docker
saavagebueno commented 2025-11-20 04:23:38 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (May 23, 2024):

That's kind of strange. The logic is to:

  1. Get all records for the domain and search for the record matching the record type (A) and the host (i.e. @)
  2. If not found, send a request to create it
  3. If found, update it

I would guess the problem lies in step 1.

Can you please check what you get from accessing https://username:token@api.name.com/v4/domains/yourdomain.com/records from your browser (and replace username, token and yourdomain.com?

I expect it to be similar to:

{
    "records": [
        {
            "id": 12345,
            "domainName": "yourdomain.com",
            "host": "@",
            "fqdn": "yourdomain.com",
            "type": "A",
            "answer": "1.2.3.4",
            "ttl": 300
        }
    ]
}

Let me know if this matches or if there is a mismatch?

You can also further debug it for me by using LOG_LEVEL=debug which logs out every http request and responses.

@qdm12 commented on GitHub (May 23, 2024): That's kind of strange. The logic is to: 1. Get all records for the domain and search for the record matching the record type (`A`) and the host (i.e. `@`) 2. If not found, send a request to create it 3. If found, update it I would guess the problem lies in step 1. Can you please check what you get from accessing `https://username:token@api.name.com/v4/domains/yourdomain.com/records` from your browser (and **replace** `username`, `token` and `yourdomain.com`? I expect it to be similar to: ```json { "records": [ { "id": 12345, "domainName": "yourdomain.com", "host": "@", "fqdn": "yourdomain.com", "type": "A", "answer": "1.2.3.4", "ttl": 300 } ] } ``` Let me know if this matches or if there is a mismatch? You can also further debug it for me by using `LOG_LEVEL=debug` which logs out every http request and responses.
saavagebueno commented 2025-11-20 04:23:38 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (May 24, 2024):

Thanks so much for a quick response; i have added all the output in a word doc for simplicity let me know if you need it plain txt.. really like your software and its saves me creating something similar in golang myself. :)
duplicate record.docx
attached a word doc with the username and api key removed and also some screen shots.. Thanks Mark

@CaptainBuzzable commented on GitHub (May 24, 2024): Thanks so much for a quick response; i have added all the output in a word doc for simplicity let me know if you need it plain txt.. really like your software and its saves me creating something similar in golang myself. :) [duplicate record.docx](https://github.com/qdm12/ddns-updater/files/15428703/duplicate.record.docx) attached a word doc with the username and api key removed and also some screen shots.. Thanks Mark
saavagebueno commented 2025-11-20 04:23:38 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (May 24, 2024):

here is the curl works perfectly see my word doc for more information.. no issues with credentials ;)

curl https://xxxxxx:xxxxx@api.name.com/v4/domains/firtreecottage.com/records

{"records":[{"id":244555916,"domainName":"firtreecottage.com","fqdn":"firtreecottage.com.","type":"A","answer":"185.254.149.99","ttl":300},{"id":244555918,"domainName":"firtreecottage.com","host":"www","fqdn":"www.firtreecottage.com.","type":"CNAME","answer":"firtreecottage.com","ttl":300},{"id":244835513,"domainName":"firtreecottage.com","host":"wireguard","fqdn":"wireguard.firtreecottage.com.","type":"CNAME","answer":"firtreecottage.com","ttl":300},{"id":244880045,"domainName":"firtreecottage.com","host":"cornwallipsec","fqdn":"cornwallipsec.firtreecottage.com.","type":"CNAME","answer":"firtreecottage.com","ttl":300},{"id":244943868,"domainName":"firtreecottage.com","fqdn":"firtreecottage.com.","type":"TXT","answer":"google-site-verification=xxxxxxxxxx,"ttl":3600},{"id":245176542,"domainName":"firtreecottage.com","fqdn":"firtreecottage.com.","type":"A","answer":"185.254.149.145","ttl":300}]}
@CaptainBuzzable commented on GitHub (May 24, 2024): here is the curl works perfectly see my word doc for more information.. no issues with credentials ;) ``` curl https://xxxxxx:xxxxx@api.name.com/v4/domains/firtreecottage.com/records ``` ```json {"records":[{"id":244555916,"domainName":"firtreecottage.com","fqdn":"firtreecottage.com.","type":"A","answer":"185.254.149.99","ttl":300},{"id":244555918,"domainName":"firtreecottage.com","host":"www","fqdn":"www.firtreecottage.com.","type":"CNAME","answer":"firtreecottage.com","ttl":300},{"id":244835513,"domainName":"firtreecottage.com","host":"wireguard","fqdn":"wireguard.firtreecottage.com.","type":"CNAME","answer":"firtreecottage.com","ttl":300},{"id":244880045,"domainName":"firtreecottage.com","host":"cornwallipsec","fqdn":"cornwallipsec.firtreecottage.com.","type":"CNAME","answer":"firtreecottage.com","ttl":300},{"id":244943868,"domainName":"firtreecottage.com","fqdn":"firtreecottage.com.","type":"TXT","answer":"google-site-verification=xxxxxxxxxx,"ttl":3600},{"id":245176542,"domainName":"firtreecottage.com","fqdn":"firtreecottage.com.","type":"A","answer":"185.254.149.145","ttl":300}]} ```
saavagebueno commented 2025-11-20 04:23:38 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (May 24, 2024):

2024-05-24T06:43:13Z DEBUG config read: {
nameddns.firtreecottage  |   "settings": [
nameddns.firtreecottage  |     {
nameddns.firtreecottage  |       "provider": "name.com",
nameddns.firtreecottage  |       "domain": "firtreecottage.com",
nameddns.firtreecottage  |       "host": "@",
nameddns.firtreecottage  |       "username": ",
nameddns.firtreecottage  |       "token": "xxx",
nameddns.firtreecottage  |       "ttl": 300,
nameddns.firtreecottage  |       "ip_version": "ipv4",
nameddns.firtreecottage  |       "ipv6_suffix": ""
nameddns.firtreecottage  |     }
nameddns.firtreecottage  |   ]
nameddns.firtreecottage  | }
@CaptainBuzzable commented on GitHub (May 24, 2024): ``` 2024-05-24T06:43:13Z DEBUG config read: { nameddns.firtreecottage | "settings": [ nameddns.firtreecottage | { nameddns.firtreecottage | "provider": "name.com", nameddns.firtreecottage | "domain": "firtreecottage.com", nameddns.firtreecottage | "host": "@", nameddns.firtreecottage | "username": ", nameddns.firtreecottage | "token": "xxx", nameddns.firtreecottage | "ttl": 300, nameddns.firtreecottage | "ip_version": "ipv4", nameddns.firtreecottage | "ipv6_suffix": "" nameddns.firtreecottage | } nameddns.firtreecottage | ] nameddns.firtreecottage | } ```
saavagebueno commented 2025-11-20 04:23:39 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (May 24, 2024):

When i delete the old duplicate entry its works no update needed.

2024-05-24T06:43:13Z INFO Found single setting to update record
2024-05-24T06:43:13Z INFO Reading history from database: domain firtreecottage.com host @ ipv4
2024-05-24T06:43:13Z DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: false
2024-05-24T06:43:13Z INFO [backup] disabled
2024-05-24T06:43:13Z INFO [http server] listening on :80
2024-05-24T06:43:13Z INFO [healthcheck server] listening on 127.0.0.1:9999
2024-05-24T06:43:13Z DEBUG your public IP address are: v4 or v6: invalid IP, v4: 185.254.149.145, v6: invalid IP
2024-05-24T06:43:13Z DEBUG ipv4 address of firtreecottage.com is 185.254.149.145 and your ipv4 address is 185.254.149.145, skipping update
@CaptainBuzzable commented on GitHub (May 24, 2024): When i delete the old duplicate entry its works no update needed. ``` 2024-05-24T06:43:13Z INFO Found single setting to update record 2024-05-24T06:43:13Z INFO Reading history from database: domain firtreecottage.com host @ ipv4 2024-05-24T06:43:13Z DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: false 2024-05-24T06:43:13Z INFO [backup] disabled 2024-05-24T06:43:13Z INFO [http server] listening on :80 2024-05-24T06:43:13Z INFO [healthcheck server] listening on 127.0.0.1:9999 2024-05-24T06:43:13Z DEBUG your public IP address are: v4 or v6: invalid IP, v4: 185.254.149.145, v6: invalid IP 2024-05-24T06:43:13Z DEBUG ipv4 address of firtreecottage.com is 185.254.149.145 and your ipv4 address is 185.254.149.145, skipping update ```
saavagebueno commented 2025-11-20 04:23:39 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (May 28, 2024):

Just check if i delete the a record before the update in name.com it works perfectly.

@CaptainBuzzable commented on GitHub (May 28, 2024): Just check if i delete the a record before the update in name.com it works perfectly.
saavagebueno commented 2025-11-20 04:23:39 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (Jun 11, 2024):

curl -u 'xxxxx:xxxxxx' 'https://api.name.com/v4/domains/firtreecottage.com/records/2460007xx' -X PUT -H 'Content-Type: application/json' --data '{"domainName":"firtreecottage.com","fqdn":"firtreecottage.com ","type":"A","answer":"10.10.10.1","ttl":300}'.

*************** This curl works ??

@CaptainBuzzable commented on GitHub (Jun 11, 2024): ``` curl -u 'xxxxx:xxxxxx' 'https://api.name.com/v4/domains/firtreecottage.com/records/2460007xx' -X PUT -H 'Content-Type: application/json' --data '{"domainName":"firtreecottage.com","fqdn":"firtreecottage.com ","type":"A","answer":"10.10.10.1","ttl":300}'. ``` *************** This curl works ??
saavagebueno commented 2025-11-20 04:23:39 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (Jun 11, 2024):

The API has changed..

curl -u 'username:token' 'https://api.dev.name.com/v4/domains/example.org/records/12345' -X PUT -H 'Content-Type: application/json' --data '{"host":"www","type":"A","answer":"10.0.0.1","ttl":300}'

{
    "id": 12345,
    "domainName": "example.org",
    "host": "www",
    "fqdn": "www.example.org",
    "type": "A",
    "answer": "10.0.0.1",
    "ttl": 300
}

Now expects this

--data '{"domainName":"firtreecottage.com","fqdn":"firtreecottage.com ","type":"A","answer":"10.10.10.1","ttl":300}'.
@CaptainBuzzable commented on GitHub (Jun 11, 2024): The API has changed.. ``` curl -u 'username:token' 'https://api.dev.name.com/v4/domains/example.org/records/12345' -X PUT -H 'Content-Type: application/json' --data '{"host":"www","type":"A","answer":"10.0.0.1","ttl":300}' ``` ```json { "id": 12345, "domainName": "example.org", "host": "www", "fqdn": "www.example.org", "type": "A", "answer": "10.0.0.1", "ttl": 300 } ``` Now expects this ``` --data '{"domainName":"firtreecottage.com","fqdn":"firtreecottage.com ","type":"A","answer":"10.10.10.1","ttl":300}'. ```
saavagebueno commented 2025-11-20 04:23:39 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jun 13, 2024):

I believe I found the problem, which is fixed with c1bf7a49c1 - can you try pulling the latest image and see if it works now?

For details, name.com responds with the "host" field absent for the root host (@), so comparing "" with "@" would fail and so the record would not be found. This is now fixed by overriding "" with "@" when going through listed records, before doing the comparison.

@qdm12 commented on GitHub (Jun 13, 2024): I believe I found the problem, which is fixed with c1bf7a49c198ce64d74bf6b7bc1e5f92ebe130cb - can you try pulling the latest image and see if it works now? For details, name.com responds with the "host" field absent for the root host (`@`), so comparing `""` with `"@"` would fail and so the record would not be found. This is now fixed by overriding `""` with `"@"` when going through listed records, before doing the comparison.
saavagebueno commented 2025-11-20 04:23:40 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (Jun 14, 2024):

Thanks so much Quentin Wow!!! , i was just about to spin up go-lang and
write one myself!!

I will pull the image and give it a go!

Simply thank you!!

On Thu, 13 Jun 2024 at 20:18, Quentin McGaw @.***>
wrote:

I believe I found the problem, which is fixed with c1bf7a4
https://github.com/qdm12/ddns-updater/commit/c1bf7a49c198ce64d74bf6b7bc1e5f92ebe130cb

  • can you try pulling the latest image and see if it works now?

For details, name.com responds with the "host" field absent for the root
host (@), so comparing "" with "@" would fail and so the record would not
be found. This is now fixed by overriding "" with "@" when going through
listed records, before doing the comparison.

—
Reply to this email directly, view it on GitHub
https://github.com/qdm12/ddns-updater/issues/724#issuecomment-2166597783,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIRUBA7WLPXJ2RKSKDWF4D3ZHHV77AVCNFSM6AAAAABH3U7HXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRWGU4TONZYGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

@CaptainBuzzable commented on GitHub (Jun 14, 2024): Thanks so much Quentin Wow!!! , i was just about to spin up go-lang and write one myself!! I will pull the image and give it a go! Simply thank you!! On Thu, 13 Jun 2024 at 20:18, Quentin McGaw ***@***.***> wrote: > I believe I found the problem, which is fixed with c1bf7a4 > <https://github.com/qdm12/ddns-updater/commit/c1bf7a49c198ce64d74bf6b7bc1e5f92ebe130cb> > - can you try pulling the latest image and see if it works now? > > For details, name.com responds with the "host" field absent for the root > host (@), so comparing "" with "@" would fail and so the record would not > be found. This is now fixed by overriding "" with "@" when going through > listed records, before doing the comparison. > > — > Reply to this email directly, view it on GitHub > <https://github.com/qdm12/ddns-updater/issues/724#issuecomment-2166597783>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BIRUBA7WLPXJ2RKSKDWF4D3ZHHV77AVCNFSM6AAAAABH3U7HXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRWGU4TONZYGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
saavagebueno commented 2025-11-20 04:23:40 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (Jun 16, 2024):

OK just pulled image: qmcgaw/ddns-updater:latest 16th June,

Now i get this..

nameddns.notinproduction  | 2024-06-16T06:54:18Z INFO ipv4 address of marklucas.co.uk is 10.10.10.10 and your ipv4 address  is 95.166.29.89
nameddns.notinproduction  | 2024-06-16T06:54:18Z INFO Updating record [domain: marklucas.co.uk | host: @ | provider: name.com | ip: ipv4] to use 95.166.29.89
nameddns.notinproduction  | 2024-06-16T06:54:19Z ERROR updating record: bad request sent: Parameter Value Error - Invalid Host: @.marklucas.co.uk

now delete a record from name.com.

completely (no A record at all) in DNS

restart

| 2024-06-16T06:58:08Z INFO [http server] http server listening on [::]:80
nameddns.notinproduction  | 2024-06-16T06:58:08Z INFO [backup] disabled
nameddns.notinproduction  | 2024-06-16T06:58:09Z INFO ipv4 address of marklucas.co.uk is 10.10.10.10 and your ipv4 address  is 95.166.xx.89
nameddns.notinproduction  | 2024-06-16T06:58:09Z INFO Updating record [domain: marklucas.co.uk | host: @ | provider: name.com | ip: ipv4] to use 95.166.xx.89
mark@docker2:/usb/nameDDNS$

Notes

"domain": "marklucas.co.uk",
      "host": "@",
@CaptainBuzzable commented on GitHub (Jun 16, 2024): OK just pulled image: qmcgaw/ddns-updater:latest 16th June, Now i get this.. ``` nameddns.notinproduction | 2024-06-16T06:54:18Z INFO ipv4 address of marklucas.co.uk is 10.10.10.10 and your ipv4 address is 95.166.29.89 nameddns.notinproduction | 2024-06-16T06:54:18Z INFO Updating record [domain: marklucas.co.uk | host: @ | provider: name.com | ip: ipv4] to use 95.166.29.89 nameddns.notinproduction | 2024-06-16T06:54:19Z ERROR updating record: bad request sent: Parameter Value Error - Invalid Host: @.marklucas.co.uk ``` **now delete a record from name.com**. completely (no A record at all) in DNS restart ``` | 2024-06-16T06:58:08Z INFO [http server] http server listening on [::]:80 nameddns.notinproduction | 2024-06-16T06:58:08Z INFO [backup] disabled nameddns.notinproduction | 2024-06-16T06:58:09Z INFO ipv4 address of marklucas.co.uk is 10.10.10.10 and your ipv4 address is 95.166.xx.89 nameddns.notinproduction | 2024-06-16T06:58:09Z INFO Updating record [domain: marklucas.co.uk | host: @ | provider: name.com | ip: ipv4] to use 95.166.xx.89 mark@docker2:/usb/nameDDNS$ ``` Notes ```json "domain": "marklucas.co.uk", "host": "@", ```
saavagebueno commented 2025-11-20 04:23:40 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jun 16, 2024):

Are you sure your "host" field is "@" and not "@.marklucas.co.uk"? 🤔
On the name.com's API UpdateRecord documentation (here), it states:

An apex record would be specified by either an empty host "" or "@"

And for now this is what's done using "@"

d3b689d0ef/internal/provider/providers/namecom/updaterecord.go (L30-L40)

The same is also done to create a record, and it seems to work which is quite strange:

d3b689d0ef/internal/provider/providers/namecom/createrecord.go (L30-L40)

Anyway, I pushed 012a6dddcd to force the host field to be "" instead of "@" when updating a record, since this may be the problem 🤔 Let me know if this resolves it 😉 Also curious about wildcards if you can check it works fine that would be great too!

@qdm12 commented on GitHub (Jun 16, 2024): Are you sure your `"host"` field is `"@"` and not `"@.marklucas.co.uk"`? 🤔 On the name.com's API UpdateRecord documentation ([here](https://www.name.com/api-docs/dns#UpdateRecord)), it states: > An apex record would be specified by either an empty host "" or "@" And for now this is what's done using `"@"` https://github.com/qdm12/ddns-updater/blob/d3b689d0ef700631a580e1a1c5a9c80a7bd6288c/internal/provider/providers/namecom/updaterecord.go#L30-L40 The same is also done to create a record, and it seems to work which is quite strange: https://github.com/qdm12/ddns-updater/blob/d3b689d0ef700631a580e1a1c5a9c80a7bd6288c/internal/provider/providers/namecom/createrecord.go#L30-L40 Anyway, I pushed 012a6dddcd388c6110e5ef0006e96c2b1ac18577 to force the host field to be `""` instead of `"@"` when updating a record, since this may be the problem 🤔 Let me know if this resolves it 😉 Also curious about wildcards if you can check it works fine that would be great too!
saavagebueno commented 2025-11-20 04:23:40 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (Jun 16, 2024):

Hello Quentin,
This now works 100% thank you so much for all your amazing help!! -
9:31Z INFO [healthcheck server] health http server listening on
127.0.0.1:9999
nameddns.notinproduction | 2024-06-16T08:59:31Z INFO [http server] http
server listening on [::]:80
nameddns.notinproduction | 2024-06-16T08:59:31Z INFO [backup] disabled
nameddns.notinproduction | 2024-06-16T08:59:31Z INFO ipv4 address of
marklucas.co.uk is 195.166.29.89 and your ipv4 address is 95.166.29.89
nameddns.notinproduction | 2024-06-16T08:59:31Z INFO Updating record
[domain: marklucas.co.uk | host: @ | provider: name.com | ip: ipv4] to use
95.166.29.89

No Errors!!! name.com + ddns-updater 10/10 :)

marklucas.co.uk @ Name.com https://name.com/ ipv4 Success (changed to
95.166.29.89), 3m43s ago 95.166.29.89 https://ipinfo.io/95.166.29.89
195.166.29.89

On Sun, 16 Jun 2024 at 09:36, Quentin McGaw @.***>
wrote:

Are you sure your "host" field is "@" and not @.***"? 🤔
On the name.com's API UpdateRecord documentation (here
https://www.name.com/api-docs/dns#UpdateRecord), it states:

An apex record would be specified by either an empty host "" or "@"

And for now this is what's done

d3b689d0ef/internal/provider/providers/namecom/updaterecord.go (L30-L40)

The same is also done to create a record, and it seems to work which is
quite strange:

d3b689d0ef/internal/provider/providers/namecom/createrecord.go (L30-L40)

Anyway, I pushed 012a6dd
https://github.com/qdm12/ddns-updater/commit/012a6dddcd388c6110e5ef0006e96c2b1ac18577
to force the host field to be "" instead of "@" when updating a record,
since this may be the problem 🤔 Let me know if this resolves it 😉 Also
curious about wildcards if you can check it works fine that would be great
too!

—
Reply to this email directly, view it on GitHub
https://github.com/qdm12/ddns-updater/issues/724#issuecomment-2171248975,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIRUBA74QV54O6LCA5PLKKDZHVFAXAVCNFSM6AAAAABH3U7HXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGI2DQOJXGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

@CaptainBuzzable commented on GitHub (Jun 16, 2024): Hello Quentin, This now works 100% thank you so much for all your amazing help!! - 9:31Z INFO [healthcheck server] health http server listening on 127.0.0.1:9999 nameddns.notinproduction | 2024-06-16T08:59:31Z INFO [http server] http server listening on [::]:80 nameddns.notinproduction | 2024-06-16T08:59:31Z INFO [backup] disabled nameddns.notinproduction | 2024-06-16T08:59:31Z INFO ipv4 address of marklucas.co.uk is 195.166.29.89 and your ipv4 address is 95.166.29.89 nameddns.notinproduction | 2024-06-16T08:59:31Z INFO Updating record [domain: marklucas.co.uk | host: @ | provider: name.com | ip: ipv4] to use 95.166.29.89 No Errors!!! name.com + ddns-updater 10/10 :) marklucas.co.uk @ Name.com <https://name.com/> ipv4 Success (changed to 95.166.29.89), 3m43s ago 95.166.29.89 <https://ipinfo.io/95.166.29.89> 195.166.29.89 On Sun, 16 Jun 2024 at 09:36, Quentin McGaw ***@***.***> wrote: > Are you sure your "host" field is "@" and not ***@***.***"? 🤔 > On the name.com's API UpdateRecord documentation (here > <https://www.name.com/api-docs/dns#UpdateRecord>), it states: > > An apex record would be specified by either an empty host "" or "@" > > And for now this is what's done > > > https://github.com/qdm12/ddns-updater/blob/d3b689d0ef700631a580e1a1c5a9c80a7bd6288c/internal/provider/providers/namecom/updaterecord.go#L30-L40 > > The same is also done to create a record, and it seems to work which is > quite strange: > > > https://github.com/qdm12/ddns-updater/blob/d3b689d0ef700631a580e1a1c5a9c80a7bd6288c/internal/provider/providers/namecom/createrecord.go#L30-L40 > > Anyway, I pushed 012a6dd > <https://github.com/qdm12/ddns-updater/commit/012a6dddcd388c6110e5ef0006e96c2b1ac18577> > to force the host field to be "" instead of "@" when updating a record, > since this may be the problem 🤔 Let me know if this resolves it 😉 Also > curious about wildcards if you can check it works fine that would be great > too! > > — > Reply to this email directly, view it on GitHub > <https://github.com/qdm12/ddns-updater/issues/724#issuecomment-2171248975>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BIRUBA74QV54O6LCA5PLKKDZHVFAXAVCNFSM6AAAAABH3U7HXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGI2DQOJXGU> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
saavagebueno commented 2025-11-20 04:23:40 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (Jun 16, 2024):

A little payment coming your way for a coffee!!

@CaptainBuzzable commented on GitHub (Jun 16, 2024): A little payment coming your way for a coffee!!
saavagebueno commented 2025-11-20 04:23:41 -05:00
Author
Owner
Copy Link

@CaptainBuzzable commented on GitHub (Jun 16, 2024):

Done!!

@CaptainBuzzable commented on GitHub (Jun 16, 2024): Done!!
saavagebueno commented 2025-11-20 04:23:41 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jun 16, 2024):

Awesome, thanks for the little 💸 👍 enjoy!

@qdm12 commented on GitHub (Jun 16, 2024): Awesome, thanks for the little 💸 👍 enjoy!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Category: Config problem 📝
Category: Database 🗃️
Category: Documentation ✒️
Category: Foolproof settings 👼
Category: Good idea 🎯
Category: Healthcheck 🩺
Category: IP fetching 📥
Category: Label missing ❗
Category: Maintenance ⛓️
Category: Motivated! 🙌
Category: New provider 🆕
Category: Provider update ♻️
Category: Shoutrrr 📢
Category: Web UI 🖱️
Category: Wildcard 🃏
Closed: ⚰️ Inactive
Closed: 👥 Duplicate
Closed: 🗑️ Bad issue
Complexity: ☣️ Hard to do
Complexity: 🟩 Easy to do
Priority: 💤 Low priority
Priority: 🚨 Urgent
pull-request
Mirrored from GitHub Pull Request
 Status: 🔒 After next release
Status: 🔴 Blocked
Status: 🗯️ Waiting for feedback
No Label Category: Provider update ♻️ Complexity: 🟩 Easy to do Priority: 🚨 Urgent Status: 🗯️ Waiting for feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#402
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?