Namecheap dynamic dns Not Updating

jimp

I pulled up a 2.0.3 VM and tried it there, worked the same, no problems. I even edited the IP in Namecheap's control panel to something bogus, then removed the cached IP from the pfSense VM and made it update again, worked fine.

Trel

@jimp:

I pulled up a 2.0.3 VM and tried it there, worked the same, no problems. I even edited the IP in Namecheap's control panel to something bogus, then removed the cached IP from the pfSense VM and made it update again, worked fine.

Does it work if the domain is one deeper, @.sub.domain.com?
(Also, how can I force it to update for testing)
(And you're leaving the username blank, right?)

jimp

Username blank, yes.

You can force an update by removing the cache file from /conf and then saving on the page.

A subdomain is not considered an @ record in their DNS that I'm aware of. It would just be sub.domain.com where sub is just a hostname in that context.

IIRC their DNS does not split that into separate "true" zones that would contain an @ record.

Trel

@jimp:

Username blank, yes.

You can force an update by removing the cache file from /conf and then saving on the page.

A subdomain is not considered an @ record in their DNS that I'm aware of. It would just be sub.domain.com where sub is just a hostname in that context.

IIRC their DNS does not split that into separate "true" zones that would contain an @ record.

sub.domain.com is what is pointed to namecheap. domain.com is pointed elsewhere.
I need to update @.sub.domain.com for it to accept it.

(I know this setup works as I came from a WRT54GL with Tomato firmware that had no issue updating)

jimp

OK. It's possible that their dyndns API has a problem with that particular setup then. I don't have anything even close to that setup to test.

I'd need to see the exact update URL used by tomato to know what might fix it.

Trel

@jimp:

OK. It's possible that their dyndns API has a problem with that particular setup then. I don't have anything even close to that setup to test.

I'd need to see the exact update URL used by tomato to know what might fix it.


	// +opt +opt +opt
	sprintf(query, "/update?host=%s&domain=%s&password=%s",
		get_option_required("host"), get_option("user") ? : get_option_required("domain"), get_option_required("pass"));

	// +opt
	append_addr_option(query, "&ip=%s");

I took this from Tomato's source.
I'm not well versed in coding, but I'm pretty sure that's where it updates to.
so in my case, it would look like:

update?host=@&domain=sub.domain.com&password=somethingcomplicated

jimp

I think I see where the problem might be, in our code, it assumes for .com (and most others) that the domain part is only domain.tld, so it's probably splitting that into @.sub for the host and domain.com for the domain.

Not sure if there will be any easy way around that, I'll have to dig at it a little.

Trel

@jimp:

I think I see where the problem might be, in our code, it assumes for .com (and most others) that the domain part is only domain.tld, so it's probably splitting that into @.sub for the host and domain.com for the domain.

Not sure if there will be any easy way around that, I'll have to dig at it a little.

That implementation looks like it could cause problems with many country tlds such as ".co.uk" or similar as "@.sub.domain.com" has the same separations as "@.domain.co.uk"

jimp

No, there is code specifically to handle domain.co.uk, there is a list in the client that knows how many levels deep TLDs go and sets exceptions based on the TLDs offered by Namecheap.

Might have to hack it so if you put in @ for the username and the actual sub.domain.com for the hostname then it would do the right thing… might be a bit before I'd have a chance to take a crack at it, I haven't touched the dyndns code in a while, it's not terribly complex though.

Trel

@jimp:

No, there is code specifically to handle domain.co.uk, there is a list in the client that knows how many levels deep TLDs go and sets exceptions based on the TLDs offered by Namecheap.

Might have to hack it so if you put in @ for the username and the actual sub.domain.com for the hostname then it would do the right thing… might be a bit before I'd have a chance to take a crack at it, I haven't touched the dyndns code in a while, it's not terribly complex though.

Since the "@" and the no username part only exists for namecheap, I can't imagine it being too difficult to do that with an if statement in general.
Other than the program the other person linked earlier, is there any interim solution I can do in the mean time?

Is curl or wget installed by default? If so I imagine I could temporarily install the cron package and do it that way.

jimp

"fetch" is there, curl may or may not be there depending on the packages you have installed.

fetch is capable of grabbing/hitting a page, e.g.:

fetch -o /dev/null http://blah.blah/blah

That would make a page request and ignore the result.

Trel

@jimp:

"fetch" is there, curl may or may not be there depending on the packages you have installed.

fetch is capable of grabbing/hitting a page, e.g.:
fetch -o /dev/null http://blah.blah/blah
That would make a page request and ignore the result.

This look good (as I'm not quite familiar with fetch)

/usr/bin/nice -n20 fetch -o /dev/null https://dynamicdns.park-your-domain.com/update?host=@&domain=sub.domain.com&password=<password></password>

jimp

Be sure to enclose the URL in quotes, but otherwise, yeah I think it looks OK.

JohnnyBeGood

I have same issue. At one point I was able to update domain.net with @.domain.net under hostname but not subdomain.domain.net
Now nothing's updating. IP ADDRESS never updates and stays at 127.0.0.1 . I deleted multiple times everything. Chatted with support but their response is to use different client or manually update ip, how will I know if it will work once IP changes??

My goal was to have unused domain for dynamic DNS.

My register is still godaddy.
If someone has it working with other service please share. I would be willing to transfer my domain there for about 10-15 per year.

Here's some screenshots:

http://i.imgur.com/3mcVlNw.png

http://i.imgur.com/72hO7Li.png

http://i.imgur.com/KjLJeyh.png

http://i.imgur.com/Hwtf55P.png

Guest

I have been using Namecheap ddns for years, had a problem once when their servers went down, but since then all is well.

I use a single subdomain.domainname.com with the subdomain record type set to A (address)

I haven't tried it with the @ hostname setting yet.

I also use the free dyndns service as a backup. I wished the pfsense service would force a connection to their server every few weeks.

Trel

Was this ever fixed for Namecheap, or do I still need to use the cron job and fetch?