[GH-ISSUE #144] Timeout when updating host #134

New issue

Closed

opened 2026-02-26 09:35:58 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:35:58 +03:00

Owner

Originally created by @seriousp on GitHub (Mar 19, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/144

Hi, I'm newbie on Github. I have problem when I try to add a new host on my domain and found message "Timeout - communicating to name server failed.".

Then, I try to sniffer packet between nsupdate.info and my auth nameserver. An output as below,

13:03:28.596766 IP 85.10.192.104.22995 > 10.2.4.145.53: 11793% [1au] SOA? ooo.mypz.in.th. (43)
13:03:28.606175 IP 10.2.4.145.53 > 85.10.192.104.22995: 11793 NXDomain_- 0/1/1 (94)
13:05:54.029521 IP 85.10.192.104.50202 > 10.2.4.145.53: 16633% [1au] SOA? bbb.mypz.in.th. (43)
13:05:54.031528 IP 10.2.4.145.53 > 85.10.192.104.50202: 16633 NXDomain_- 0/1/1 (94)

nsupdate send packet to check this host(bbb.mypz.in.th) to my auth nameserver but don't send any update packet.

I try to update with nsupdate command on linux and I found a correct flow as below,

13:15:56.318991 IP 122.155.55.58.7654 > 10.2.4.145.53: 12093 [1au] SOA? demo.mypz.in.th. (148)
13:15:56.320380 IP 10.2.4.145.53 > 122.155.55.58.7654: 12093 NXDomain*- 0/1/1 (199)
13:15:56.371160 IP 122.155.55.58.7654 > 10.2.4.145.53: 8253 update [1n] [1au] SOA? mypz.in.th. (164)
13:15:56.432053 IP 10.2.4.145.53 > 122.155.55.58.7654: 8253 update- 0/0/1 (143)
13:15:56.434734 IP 10.2.4.145.53500 > 210.213.38.82.53: 52951 notify [b2&3=0x2400] [1a] SOA? mypz.in.th. (79)
13:15:58.437486 IP 10.2.4.145.53500 > 210.213.38.82.53: 12764 notify [b2&3=0x2400] [1a] SOA? mypz.in.th. (79)
13:16:00.439431 IP 10.2.4.145.53500 > 210.213.38.82.53: 21279 notify [b2&3=0x2400] [1a] SOA? mypz.in.th. (79)
13:16:02.441682 IP 10.2.4.145.53500 > 210.213.38.82.53: 6579 notify [b2&3=0x2400] [1a] SOA? mypz.in.th. (79)

Finally, Could you suggest me to solve this problem ? Many thanks for you and your dev.

Sorry, for my english
Best Regards,

Originally created by @seriousp on GitHub (Mar 19, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/144 Hi, I'm newbie on Github. I have problem when I try to add a new host on my domain and found message "Timeout - communicating to name server failed.". Then, I try to sniffer packet between nsupdate.info and my auth nameserver. An output as below, 13:03:28.596766 IP 85.10.192.104.22995 > 10.2.4.145.53: 11793% [1au] SOA? ooo.mypz.in.th. (43) 13:03:28.606175 IP 10.2.4.145.53 > 85.10.192.104.22995: 11793 NXDomain_\- 0/1/1 (94) 13:05:54.029521 IP 85.10.192.104.50202 > 10.2.4.145.53: 16633% [1au] SOA? bbb.mypz.in.th. (43) 13:05:54.031528 IP 10.2.4.145.53 > 85.10.192.104.50202: 16633 NXDomain_\- 0/1/1 (94) nsupdate send packet to check this host(bbb.mypz.in.th) to my auth nameserver but don't send any update packet. I try to update with nsupdate command on linux and I found a correct flow as below, 13:15:56.318991 IP 122.155.55.58.7654 > 10.2.4.145.53: 12093 [1au] SOA? demo.mypz.in.th. (148) 13:15:56.320380 IP 10.2.4.145.53 > 122.155.55.58.7654: 12093 NXDomain*- 0/1/1 (199) 13:15:56.371160 IP 122.155.55.58.7654 > 10.2.4.145.53: 8253 update [1n] [1au] SOA? mypz.in.th. (164) 13:15:56.432053 IP 10.2.4.145.53 > 122.155.55.58.7654: 8253 update- 0/0/1 (143) 13:15:56.434734 IP 10.2.4.145.53500 > 210.213.38.82.53: 52951 notify [b2&3=0x2400] [1a] SOA? mypz.in.th. (79) 13:15:58.437486 IP 10.2.4.145.53500 > 210.213.38.82.53: 12764 notify [b2&3=0x2400] [1a] SOA? mypz.in.th. (79) 13:16:00.439431 IP 10.2.4.145.53500 > 210.213.38.82.53: 21279 notify [b2&3=0x2400] [1a] SOA? mypz.in.th. (79) 13:16:02.441682 IP 10.2.4.145.53500 > 210.213.38.82.53: 6579 notify [b2&3=0x2400] [1a] SOA? mypz.in.th. (79) Finally, Could you suggest me to solve this problem ? Many thanks for you and your dev. Sorry, for my english Best Regards,

kerem closed this issue

2026-02-26 09:35:59 +03:00

kerem commented

2026-02-26 09:35:59 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Mar 19, 2014):

thanks for reporting this. i had seen your problems and left a comment in the domain record.

this might be related to / a duplicate of #140 and / or #108 - if you have ip v6, you could try that, but it likely still won't work due to the other issue.

@ThomasWaldmann commented on GitHub (Mar 19, 2014): thanks for reporting this. i had seen your problems and left a comment in the domain record. this might be related to / a duplicate of #140 and / or #108 - if you have ip v6, you could try that, but it likely still won't work due to the other issue.

kerem commented

2026-02-26 09:35:59 +03:00

Author

Owner

@seriousp commented on GitHub (Mar 21, 2014):

lol I don't have an ip v6.

@seriousp commented on GitHub (Mar 21, 2014): lol I don't have an ip v6.

kerem commented

2026-02-26 09:35:59 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (May 28, 2014):

see the "site notes" at the bottom of the nsupdate.info site, they show a way how to make a ipv6 address from your v4 address.

@ThomasWaldmann commented on GitHub (May 28, 2014): see the "site notes" at the bottom of the nsupdate.info site, they show a way how to make a ipv6 address from your v4 address.